syklemil

I think most of us would consider that an eclipse bug, but yeah, until it's fixed it'd make sense to work around it.

Kinda similarly, I have a mostly identical setup on several machines, and on one of them Firefox has a memory leak, which even showed up just recently. It also seems to manifest if I have certain pages open, the most noticeable of which is Reddit.

It's the kind of stuff I could dig into, buuut it's just a PITA.

Or bat, which will just print <binary> in those cases

Oliven, Norwegian. For some reason it's an uncountable noun.

It's pretty much just old Finnish territory, I'm sure it was part of Karelen at some point. Russia should give it back (or would that be mean to the Finns)

Ah yes, traditional urban cores, historically entirely without any good food options, either delivered, on the go, or even sit-down at odd hours

As if anyone cared if they had to wait a total of 3 seconds in a workday.

That depends on when it appears. Some tasks kind of have to feel instantaneous, and there might be a pretty slim margin between okay and frustrating.

But yeah, that's the kind of savings that mostly matter on the scale of regional or national grid planning.

Most engineers already write bloated, abstracted, glacial code that burns CPU cycles like a California wildfire. Clean code? Ha! You’re writing for other programmers’ academic circlejerk, not the hardware.

It’s interesting that everybody else preaches ‘Write for the human first, for the machine second’.

Yeah, the author seems to lean too hard into the "programming is electronics" model, where the opposing end is "programming is math and formal logic"; most of us take some mixed view. And most of us have higher correctness requirements than what a reasonable effort in memory unsafe languages like C and C++ gives us, so we trade away some machine efficiency. In the authors parlance, most of us aren't interested in the demoscene circlejerk; we need to make tradeoffs between maintainability and everything else. Write-once code isn't good enough.

There have been attempts at establishing a third pole of "promptgramming is natural language" or whatever ever since COBOL promised programming in plain English, but the ambiguity of natural language when used to encode a business logic machine means that a "sufficiently advanced compiler" will have to be extremely advanced, on the order of including the manager and the entire engineering methodology.

I think some of the stuff you worry about as a kid will just arise naturally. Ideas like not stepping on cracks, or imagining monsters in dark places are likely produced spontaneously and naturally by an underdeveloped ape brain.

But it'd be nice if we didn't tell kids about old superstitions, yeah. Wait until they're old enough to react with dismissal about the stupid stuff people used to believe.

The translation here actually makes it come off as more normal than the orange slime-eel currently in office

Yep. The colour theory stuff in there makes MBTI and horoscopes look detailed and well-documented in comparison

Yeah, road wear scales with mass⁴ afaik, so if the average bike with biker weighed 100kg (it doesn't) and the average car weighed 1000kg (it doesn't) you'd need 10000 bikes to make as much impact as that one car. Since cyclists are generally lighter and cars heavier, the ratio is much higher.

I would also imagine that the lower speeds and acceleration a cycle is involved in contributes—the tyre just isn't subjected to as much force.

I've been using neovim for years (and the vim family for decades), and I guess with LSP it's pretty much an IDE these days.

You'll likely also want to check out ruff for linting and formatting, by the same company that makes uv. It doesn't enable a lot of lints by default, but there's a long list of checks to enable.

They also have a typechecker, ty, which is still in early alpha. If it's as good as their other tools I expect it to become the standard for typechecking Python. Currently you'll likely want to go with pyright for that.