> No borrow checker. No lifetimes. No fighting the compiler for 20 minutes over a string.

It's embarrassing. If the borrow checker and lifetimes are difficult for the author, I would suggest sticking with non-systems-languages. In systems languages you have to either do the work the borrow-checker does in your head, or you let Rust do it.

If you are fighting the Rust compiler for 20 minutes over a string (or whatever actually happened that warrants this hyperbole), you are simply not writing good systems-level code.

This is an advanced version of the kind of person who deliberately compiles without warnings in C because they make it harder to find the error messages. It's complete amateur hour and it's embarrassing.

The real fix here is to learn how to do it properly. I VERY RARELY run into Rust compilation issues where I think "this is stupid". Nearly all of the time, the compiler is telling me that I forgot to think of something that I should have been thinking about, or that I've not been explicit enough. I've written C++ for way too long to know that this is hyper valuable.

I've also written enough Zig to know that Zig is not for people who are bad at systems level programming. It'll blow up in your face, just like C.