4 ms·
Any HN post mentioning C++ will inevitably be invaded by the Rust Evangelism Strikeforce.
by sayusasugi 7y ago
Any HN post mentioning C++ will inevitably be invaded by the Rust Evangelism Strikeforce.
- wutbrodo 7y agoYou picked a bizarre article to make that comment on...It's hardly irrelevant to the post, as the author's central thesis is that there's no case for choosing C++ over languages like Rust and Swift (he says as much in the article).
- throwupaway123 7y agoThe Rust Evangelism Strikeforce only exists in completely inane comments like yours, maybe instead of posting memes you comment on the actual content of the article not the headline?
- insulanian 7y agoAnd rightly so! What's wrong with spreading awareness about safer alternative? If that wasn't the case in the past, we'd still be programming in Cobol and Fortran.
- pjmlp 7y agoOn the contrary, we had plenty of safer alternatives for systems programming, derived from Algol and PL/I. Then came an OS, with a symbolic price instead of the typical market prices of competing OSes, alongside source code tapes, and a systems programming language that was the "JavaScript" of system languages.
- 0815test 7y agoThe biggest factor was that the OS was written to run on minicomputers as opposed to big iron, and was written in a portable language. Thus it could seamlessly jump over to micros (as soon as these became powerful enough, of course), and even later on to embedded and "wearable" compute. You just can't do that unless you're writing in a highly flexible and highly portable language - more like the FORTRAN of systems languages than anything like JavaScript!
- pjmlp 7y agoIronically, systems written in hardware 10 years older than PDP-11, thus with less resources, were written in safer system languages, go figure.