What does that have to do with anything?

You could also just alias find back to ^find. I don't use nushell as my daily driver for other reasons, and I agree with the comment above that it's a bit questionable for them to have a built-in with that name, but I don't understand why you'd even try out a new shell, let alone one that's radically different from POSIX-style shells, much less complain online about the shell you just tried, when you're already happy with the shell you're using and are not willing to adapt any habits or explore the configuration options to match your needs.

Sure, Old English. But the commenter isn't writing in old or even middle English.

Pretty much all languages are middleware, and most of the original code was shell/bash.

What? I genuinely do not know what you mean by this.

Yeah, I was particularly glad to see the change in loop variable semantics become a stable part of the language. That was a terrible footgun.

There are other things I dislike about Go, but I do think it's improving while maintaining its better qualities, which is no small feat.

It's probably not "provable" one way or the other, but I'd like to see more empirical studies in general within the software industry, and this seems like a fruitful subject for that.

For what it's worth, Ada and Spark are listed separately in the Wiki article on dependent typing. Again, though, I'm not a language expert.

I mean, at least you acknowledge that you're presenting an opinion. This blog post just tries to gloss over the fact that it's pure speculation.

Oh, right, yes; of course it statically links the standard library. I was thinking of the fact that the standard lib is precompiled, but yes, it's statically linked.

We can create rules and a human can understand if they are breaking them or not...

So I take it you are not a lawyer, nor any sort of compliance specialist?

They aren't thinking about it and deciding it's the right thing to do.

That's almost certainly true; and I'm not trying to insinuate that AI is anywhere near true human-level intelligence yet. But it's certainly got some surprisingly similar behaviors.

Doesn't squashing on merge achieve exactly the same thing? (As long as pull requests are kept small, of course.)

My understanding was that there's some ecosystem bifurcation, somewhat like Rust's. But I'll look into it again!