I believe that Rust users are past caring about that. If you feel that C is a good language for your needs, then by all means, use it. I know that Rust brings

I believe that Rust users are past caring about that. If you feel that C is a good language for your needs, then by all means, use it. I know that Rust brings me a very efficient safety net that lets me concentrate on the algorithm [1] without having to also spend quite as much time auditing, fuzzing, valgrinding and {thread, memory, ...} sanitizing my code. In addition to the safety added by the type-system, I also enjoy the convenience of tools such as `Drop`, or the ability to derive (de)serializers for most formats, etc. This is not about criticizing C. This is about picking the best tool for the job. Sometimes, it is Rust. Sometimes, it is TypeScript. I haven't encountered a job for which C was the best tool for me in a while. I'm sure that there are cases, mind you, but I don't encounter them anymore. [1] With caveats, of course. As all Rust users, I need to please the borrow-checker gods.