3 ms·
I don't know about you, but I always found Rust a real pain to use. One could say Rust is "secure", but you can still break Rust too. Incompetency knows no boun
by nercht12 9y ago
I don't know about you, but I always found Rust a real pain to use. One could say Rust is "secure", but you can still break Rust too. Incompetency knows no bounds. It's better just to learn to be competent than complain it's not dumbed-down enough for one's way of thinking. Hence, I should still learn Rust, and you can still learn C.
- irundebian 9y agoI think there so reason to be competent, whatever you mean it, to complain about C. What I learned about C is that you can never be competent enough for it. And that's the problem. A technology which isn't designed to get under control by humans under a reasonable amount of time is bad. C is an old language, designed with the knowledge in the 70 and influenced by the needs of the later decades. At its time it was revolutionary, but today it's not fulfilling our needs. I'm not talking about theoretic problems of C. C vulnerabilities are hunting us from day to day. Everyone is knowing that, but people still find it cool to code in C, want to be competent in C or dare to write security-critical applications in C, as though nothing had happened. I don't want to be competent in C, because it's overly complex and it's error prone for humans to write safe, secure and readable C code. And every good software developer should know that's wise to don't use overly sophisticated technologies.