John

You forgot to add #JumpropeColonoscopy. You are missing a huge target audience there.

Watching this play out in front of our eyes in the Linux kernel. It is good to have a governing board, but no one person should decide the fate of software that runs the world.

On a side note, the more Rust code that gets into the kernel, the less of a need there will be for Oracle Linux and RedHat Linux, both of which make their money fixing bugs in the Linux kernel. No shade on either company, I used to work for Oracle with their Linux distro. It's excellent.

Sure, the syntax can be wordy, but every bit of that wordiness is meant to specify the contracts you are making and the behavior you expect. I would rather do that in annotations than in boilerplate code, where I can make more mistakes.

I have recently starting rewriting performance and security critical features in Outlaw Practice in Rust, and I have to say that I find it a breath of fresh air. Strong typing, performance and security-first idiomatic programming. It makes it hard to screw up.

It is fascinating watching the Rust vs C debate with the Linux kernel maintainers. Both sides have good arguments, but I see the Rust maintainers bending over backwards to make it as painless as possible to work with Rust, and I see the C diehards refusing to give an inch.