BatmanAoD
There is only one mention of Python being slow, and that's in the form of a joke where Python is crossed out and replaced with "the wrong tool for the job." Elsewhere in the post, Python is mentioned more positively; it just isn't what's needed for the kind of gamedev the author wants to do.
I'm addressing the bit that I quoted, saying that an interpreted language "must" have valid semantics for all code. I'm not specifically addressing whether or not JavaScript is right in this particular case of min().
...but also, what are you talking about? Python throws a type error if you call min() with no argument.
Without one, the run time system, must assign some semantics to the source code, no matter how erroneous it is.
That's just not true; as the comment above points out, Python also has no separate compilation step and yet it did not adopt this philosophy. Interpeted languages were common before JavaScript; in fact, most LISP variants are interpreted, and LISP is older than C.
Moreover, even JavaScript does sometimes throw errors, because sometimes code is simply not valid syntactically, or has no valid semantics even in a language as permissive as JavaScript.
So Eich et al. absolutely could have made more things invalid, despite the risk that end-users would see the resulting error.
Interesting; I had assumed the executive order was intended to make the name apply to the entire gulf, but the Mexican President's phrasing of "stick to what the United States government approved" seems to contradict that, so I looked it up, and indeed it does acknowledge international boundaries within the gulf (emphasis mine):
...the Secretary of the Interior shall... rename as the “Gulf of America” the U.S. Continental Shelf area bounded on the northeast, north, and northwest by the States of Texas, Louisiana, Mississippi, Alabama and Florida and extending to the seaward boundary with Mexico and Cuba in the area formerly named as the Gulf of Mexico.
The user who submitted the report that Stenberg considered the "last straw" seems to have a history of getting bounty payouts; I have no idea how many of those were AI-assisted, but it's possible that by using an LLM to automate making reports, they're making some money despite having a low success rate.
Every single time I've tried to work on a file using tabs, I've had to configure my tabstop to be the same width the original author used in order to make the formatting reasonable. I understand that in theory customizable tabstops is preferable, but I've yet to see it work well.
(For what it's worth, I think that elastic tabstops, had they been the way tabs worked in text files to begin with, would have been far preferable.)
The biggest issue for me was that 3rd-party config broke a few times; I think carapace (which I no longer use anyway, for other reasons) was a major one.
I think that's fine; I don't usually orphan background jobs, but I do relatively often have reason to have them while I do something else. And relying on pueue for more complex uses seems more than reasonable.
I didn't realize Nu had gotten any form of job control; that was one of the limitations that forced me back to a traditional shell last time I tried it.
Looks like they're still making frequent breaking changes, though, which was another thing I found difficult to manage.
They explained pretty clearly that they use Linux exclusively for work.