I agree, but let's remember how young rust is, how little experience people have with it and its paradigms and how much they are used to code with c/c++. How c

I agree, but let's remember how young rust is, how little experience people have with it and its paradigms and how much they are used to code with c/c++. How course it's hard for them right now. Guess what, it was harder when they started c/c++ decades ago. There was less tooling, best practices were even less clear, all code bases looked different and the language ergonomics were way worse than today. Give it some time. Some time for the language to mature of course. But more than that, some time for the dev to actually reach fluency, not only it the language and ecosystem, but on the general philosophy of this way of producing software. It's even harder given many have to unlearn years of experience and patterns that made them productive, and adopt, discover, or even even new ones to replace them. We have hugely high expectations towards rust because of the amazing work the core team has already made in so little time. I see the same reaction toward the last 2 flight crashes. People are shocked this can happen. I'm just amazed it doesn't happen more often. The institutions have generally done a fantastic job. Now to say we should not fix what's broken in both cases. But let's be fair to the incredible result we already got.