None of the proposals would have banned AI usage in upstream projects, but banning AI usage in the context of the Debian project was on the table

What is the AI policy of Arch? I ask because I was unable to find any explicit policy for the project

None of the proposals would have banned AI usage in upstream projects:

https://www.debian.org/vote/2026/vote_002

Bond is not such a bad example, because he introduces himself as "Bond. James Bond", not as "Bond. Bond James". If he did introduce himself as such, then you'd be forgiven for thinking that his given name was "Bond".

The problem is also not the short form of author names, which as you point out places the family name first, and which typically abbreviate the given names. The problem is that many sites will reverse that order when they render the full names. The solution is simply to allow the authors to specify how their full name should be rendered. This not a problem that is unique to scientific journals.

The full article is available here: https://archive.ph/1NGkF

See also https://shinesolutions.com/2018/01/08/falsehoods-programmers-believe-about-names-with-examples/

Betteridge's law of headlines:

Any headline that ends in a question mark can be answered by the word no

It can't be quite that bad; they've been shipping the rust version of Bun with Claude Code since v2.1.181 (released June 18th), and I haven't seen an outcry over all related functionality breaking

I can't believe that Rust developers would call POSIX functions to interact with the operating system! The audacity!

It’s probably easier to strip down GRUB, than it is to resurrect and add missing features to a project that has been dead for 10+ years

I also saw a 4.5 second boot time speedup from installing mine. I have NO IDEA how, but it’s happened.

If I saw a speedup that I didn’t understand, then I’d worry that I had accidentally broken something. It’s easy to get speedups by not doing things correctly

At this point the people complaining about Rust at every opportunity have become more annoying than the "rewrite it in Rust" people ever were

The article is about an internal kernel API: They can easily rename those, since they are not exposed to user-space.

But you seem to be talking about the kill command and/or the kill function, that are part of the POSIX and C standards, respectively. Renaming either would break a shit-ton of code, unless you merely aliased them. And while I agree that kill is a poor name, adding non-standard aliases doesn't really offer much benefit

I set the timestamps of my music to its original release date, so that I can sort it chronologically... OK, I don't actually do that, but now I'm tempted