‘”I have written only one Rust program, so you should take all of this with a giant grain of salt,”

I will listen to his sound advice and not take it very seriously.

I don't know how else they could react:

And the compiler was slow, the code that came out was slow…

The compiler is slower because it has more to check for, but "the code that came out was slow" seems like nonsense, exaggeration, or PEBCAK. Rust code is highly performant and very close to C code.

The support mechanism that went with it — this notion of crates and barrels and things like that — was just incomprehensibly big and slow.

Dude what? C's build systems like cmake are notoriously unfriendly to users. Crates make building trivial compared to the ridiculous hoops needed for C.

I have written only one Rust program, so you should take all of this with a giant grain of salt,” he said. “And I found it a — pain… I just couldn’t grok the mechanisms that were required to do memory safety, in a program where memory wasn’t even an issue!

He doesn't say what the program was, and the borrow checker operates by a set of just a few extremely simple rules. There's no idea of what he was trying to accomplish or how the borrow checker impeded that.

So my reaction as someone who cares deeply about how disastrously unsafe C is and the tangible havoc it creates in modern society:

• I agree the compiler is slower. Honestly boo hoo. It's slower for two very good reasons (better static analysis and better feedback).
• The code being slower is such a minor issue as to effectively not be true. Benchmarks prove this.
• I'm not going to take "big and slow" as a serious critique of Cargo from someone who idealizes C's ridiculous, tedious, convoluted build system.
• The borrow checker is trivial, and unlike C, the compiler actually gives you easy, intuitive feedback for why your code doesn't build.

What honest criticisms did you find in this article? All I saw was;

• compiling is slow
• borrow checker is complicated

This isn't new?

People stopped taking Brian seriously when he helped create Go. That was pre-Rust.

Even the "talking points" here seem to be re-used from "Go vs. X" ones. Also, his experience speaks of someone who only tried Rust pre-v1.0.

Anyone who actually knows Rust, anti- or pro-, knows that what he said (partially in jest) is factually wrong.

Feel free to prove otherwise, especially the part about the performance of Rust programs. Don't be surprised if he simply didn't pass --release to cargo build, a common pitfall for someone in the "hello world" stage of trying Rust.

And this is why appeal to authority was never more fallacious, considering we live in a world where Dunning-Kruger is a universal reality.

You call that a criticism? It's a first impression.

he said he never heard of Nix or NixOS. that's it. it's a dumb article that just poorly sums up a few youtube videos of his talk.