I think you're misunderstanding that paragraph. It's specifically explaining how LLMs are not like humans, and one way is that you can't "nurture growth" in them the way you can for a human. That's not analogous to refining your nvim config and habits.

Same

I've never understood the hatred for Teams. I don't particularly like Slack, and Teams (from my limited experience using it) doesn't seem that much worse.

Nope. It links to an explanation of what that poster is:

This is the UNIX Magic Poster, originally created by Gary Overacre in the mid-1980s and published by UniTech Software.

The article is more about the behavior of members of the C++ committee than about the language. (It also has quite a few tangents.)

I read "happy ___ starts with ___" as stating that happiness was the eventual result of a process that started with ___.

He spent four years as the project maintainer. That's hardly "flouncing off."

See also Asahi Lina's thread on this, which explicitly says that Rust is one reason why their drivers cause fewer kernel panics than others: https://vt.social/@lina/113045456734886438

It's probably just easier to do all arithmetic in bc so that there's no need to analyze expressions for Bash support and have two separate arithmetic codegen paths.

The animation that goes with this is pretty slick: https://x.com/Phantom_TheGame/status/1748457358521426375?s=20

Oh hey, it's modern ed!

There are a fair number of them: https://en.m.wikipedia.org/wiki/Non-English-based_programming_languages

But arguably, as long as the compiler supports unicode, it shouldn't matter that much what language the keywords are in. There are other more important issues impacting how easy it is to program in non-English languages:

• availability of documentation and tutorials
• English comments and API names in common libraries, especially the standard library
• tooling for handling unicode, especially BiDi (which is part of why Arabic is especially tricky) - Vim, for instance, has had an open issue about this for almost a decade: https://github.com/vim/vim/issues/204