RUnconcerned

It sounds like you need to learn how to program without using a LLM, but even if you used one to write a parser, and it took you 100 requests to do so, you would very quickly get the desired energy savings.

This is the kind of thinking that leads to modern software being slower than software from 30 years ago, even though it is running on hardware that's hundreds of times faster.

That's... not a TV, it just has TV in its name.

The idea that these centibillionaires do not have "real wealth" is beyond absurd

Well, by weighing and logging everything. You are correct that it takes a lot longer when you do that. That's the cost of keeping track of your caloric intake. I also do not account for any nutrient loss or divergence from different cooking times, leftovers, or from different species.

I only weigh everything I eat when I am actively trying to lose weight, however, and when I am doing so I deliberately restrict my diet to meals where I won't waste a lot of time weighing everything. If I'm trying to maintain or gain weight, I don't really bother with it.

If multiple lines have equal-ish winning probability, rather than a single line, then you can sort of translate it to "human" complexity.

I think that's not quite the point. Leela has an advantage over AB chess engines, where it has multi-PV for "free", meaning it will evaluate multiple lines by default at no cost to performance (traditional engines, like Stockfish, will lose elo with multi-PV). This allows us to know at a glance if a position is "draw/win with perfect play" or if there is margin for error. If Leela shows multiple moves where one side maintains a winning advantage/losing disadvantage/equality, we can use that as a computer-based heuristic to know if a position is "easy" to play or not.

I mean, he was mentally ill. He was literally a victim of MKULTRA. That does not necessarily disqualify everything he wrote, however.

I... don't think that AngularJS + third-party scripts was what OP meant by plain Javascript.

It is! Whenever I play OpenTTD, I make sure to fetch the original soundtrack instead of the new one.

I'm very fond of end-to-end system tests, with any external dependencies mocked out using something like Wiremock for HTTP calls, and containers for databases or queues. If it were up to me, I'd only have that kind of test, and some unit tests for pure functions/methods that may have finicky logic.

You misunderstood my point about the `job`/`jobId`, though. It would be correctly typed, and wouldn't break anything. But it would not be immediately clear for a developer working on that code in the future if it was an instance of Job or the ID of a job, and there would be no type information that immediately makes that clear.

I don't feel like the point you are making with regards to changing the signatures is true, either. If you're changing the shape of some data structure, or adding/removing parameters, then you would also have to make those changes in a dynamically typed language, it's only when you're changing the types of the parameters that you have to make a change, but that's really not that big of a deal, since your development environment should helpfully point out the places you need to update as you change them. I value code that's easy to makes changes in, but I value code that someone else can quickly pick up more.

I totally disagree. I think not having static types is a drag on productivity and maintainability. I have to work with both Kotlin and Ruby codebases, and the Ruby ones are always a nightmare whenever you need to make a change deep within the application's core, even though the Ruby one has more extensive tests.

The idea that test coverage is a replacement for static types is nonsensical. I won't insult your intelligence and say that by great test coverage you meant testing the shape of your inputs, because only an idiot would say that would serve as a replacement for something that is done automatically by a compiler, but sometimes minor naming mistakes (like `job` instead of `jobId` when you're passing an ID and not an instance of `Job`) will make it past code review and will place a totally unnecessary mental burden on the next programmer who has to look at the code and figure out what exactly he's looking at. With static types there is no need for that, it's right there in the code.

Regardless of Star Citizen being a huge scam, a Hackernews encountering a site that does not look like all the b2b SaaS sites and being surprised that it managed to raise money is extremely funny.

feds literally fund signal

https://www.mintpressnews.com/the-open-technology-fund-makes...

first good advertisement for bluesky i've seen

Famously, no one has ever had Python environment problems :D

Not only are Marvel movies slop, they are very concentrated slop. The only way to increase the concentration of slop in a Marvel movie would be to ask ChatGPT to write the next one.

You're going to have a hard time maintaining an acceptable ratio on a non-ratioless private tracker without a seedbox or a NAS/homelab that's on 24/7. These trackers largely self-select for power users.

The message must not be getting through to the grid operators, then.

"and then crushes it with a pressure equivalent to an adult Arabian horse standing on a quarter", what a bizarre comparison, this seems like an incomprehensible reference point for most people (myself included)

Of course we do, the taxes are listed in the receipt. We just know how much we are paying ahead of time.

Stockfish has not incorporated ideas from AlphaZero. Stockfish's NN eval technology, NNUE, comes from Shogi and it predates Alphazero there.

The 2nd strongest engine, Leela Chess Zero, is indeed directly inspired by AlphaZero, though, and did surpass Stockfish until NNUE was introduced.

Reminded me of the "Torment Nexus" tweet:

https://twitter.com/AlexBlechman/status/1457842724128833538

> @AlexBlechman

> Sci-Fi Author: In my book I invented the Torment Nexus as a cautionary tale

> Tech Company: At long last, we have created the Torment Nexus from classic sci-fi novel Don't Create The Torment Nexus

> Given that most giant tech-platforms heavily conform to and moderate with a target of left-leaning values, I'd wager that deliberate control does exist.

You and I must have a fundamentally different definition of "left-leaning values".

Gmail was launched on April 1st and at the time it seemed like an April Fools prank - how could Google possibly give you 1GB of storage for free?

Two can play that game: if the Israeli government didn't want their civilians to be killed, then they wouldn't occupy Palestine. As they don't care for israeli lives, they conscript every adult into their military, making them all valid targets.

They didn't want to kill the aid workers, but the evil AI made them do it.

The GPL has more strings attached than the LGPL.

Audio software will typically allow you to configure a soft takeover, where you must move the fader or knob until it matches the software value, and only then does it take over, to eliminate these surprises.

Rotary encoders are just not as good for controlling volume as faders.

I too am a big fan of having my computer hallucinate incorrect information.

Personally when I am parsing structured data I prefer to use parsers that won't hallucinate data but that's just me.

Also, don't parse HTML with regular expressions.