Believe me, whitespace-correct scripting is absolutely an issue.

You're right that it's annoying when filenames diverge right at a character that must be escaped.

Here it is:

Presumably, it already used SIMD, and that's how the existing GNU utility beat Rust by a factor of 17x.

Presumably, it already used SIMD, and that's how the existing GNU utility beat Rust by a factor of 17x.

Oh, I see, so you don't exercise your muscle memory but you at least see the "raw" commands more often.

Looks like this was suggested in nushell, and someone came up with a way to emulate the behavior manually: https://github.com/nushell/nushell/issues/5552#issuecomment-2113935091

Edit: there's another issue for this: https://github.com/nushell/nushell/issues/5597

Hopefully nu will decide to implement it properly in the future.

Oh. Well, in that case, his resignation message was pretty matter-of-fact, not dramatic. He did link, in a note at the end of the email, to the now-infamous "the fact is, you're not going to force everyone to learn Rust" video, and the drama was more or less self-manufacturing from there. But to be honest, I think it's a good thing that more people are seeing that video than otherwise would have, and I can't really blame him for linking to it.

And isn't it somewhat concerning that bringing Rust to the kernel is still so controversial and highly "political", several years after initial approval by Linus and Greg KH?

The goal is rather to not need to think as hard...

Or, if one prefers, having more flexibility to choose how and where to allocate mental energy, rather than letting the language force you to spend some amount on the "bookkeeping" necessary to avoid various footguns.

Yeah, I mean, I tried to be explicit that I wasn't recommending unity builds. I'm just pointing out that OP, while misinformed and misguided in various ways, isn't actually wrong about header files being one source of slowness for C++.

That's the mrustc project the author mentions. He wants Rust to be bootstrapped earlier in the process.

I'm a Rust fan, and I do think they eventually struck a pretty good "visibility vs noise" balance with ? (which was highly controversial at the time).

What...? That is a terrible idea.

I guess I read his point more as being that it's effectively impossible for a license or CLA to distinguish "good" freeloaders from "bad" freeloaders, so it was inevitable that businesses would start doing license "rug-pulls" like the examples he gives.

You're misunderstanding the posts you're explaining. Sanitizers, including ASan, HWASan, and bound sanitizer, are not "static analysis tools". They are runtime tools, which is why they have a performance impact. They're not intended to be deployed as part of a final executable.

I don't know how you can read this sentence and interpret it to mean that they "haven't onboarded AddressSanitizer":

In previous years our memory bug detection efforts were focused on Address Sanitizer (ASan).