3 ms·
I don't think C++ would become obsolete any time soon, right?
by Aardwolf 12y ago
I don't think C++ would become obsolete any time soon, right?
- Agathos 12y agoPlease do not taunt the Rust fans.
- kibwen 12y agoI can tell you that Rust fans have a healthy respect for C++. There's nothing like trying to compete with C++ that makes you appreciate just how good it is at its domain (even if it does basically punt on safety (turns out it's a Hard Problem))! Trust me, if Mozilla were merely trying to exploit the depressing SV hype cycle, they'd have built a pretty-looking dynamic language rather than anything with semicolons. :P
- deleted 12y ago[deleted]
- kibwen 12y agoNot a chance. It's possible that the rate of new projects written in C++ could decline as other languages attempt to eat its lunch (disclaimer: I'm a big Rust fan, and this is exactly what we're trying to do), but C++ is a titanic industry juggernaut. Code doesn't just go away, and even bad code only needs to work "well enough" in order to make it virtually impossible to muster the political will to mount a rewrite.
- sspiff 12y agoPeople who grok C++ will be able to manage whatever would ever replace it.
- kyllo 12y agoExactly. The Rust team is trying to give C/C++ devs a better, safer, and at least equally performant tool to use. They're not trying to replace one group of people (C/C++ devs) with a different group of people (Rust devs). The fact that it's also attracting the interests of Ruby and Python devs (who may have found C/C++ scary) is a bonus.
- Gurkenmaster 12y agoThe huge C++ codebases won't vanish even if Rust becomes the most popular programming language.
- blt 12y agoGood C and C++ programmers understand how computers work. We will always need programmers who understand how computers work. I believe a cleaner language will replace C and C++ for new projects some day, but it will still present the same fundamental environment to the programmer: manual memory management, raw OS threading, ability to bit bash and do unsafe stuff if you need to. This language will not radically change the C/C++ programming model. Rather, it will add semantic power to reason about safeness, purity, concurrency, memory layout, etc. as part of the language. (I think Rust might be this language.) IMO, active C/C++ programmers should be learning more about stuff like OOO and superscalar CPU architectures, caches, NUMA, hardware atomic operations, drivers, etc. I think "C/C++ programmer" really means "close to the metal programmer working on a mainstream project," and that category will remain strong through language changes. On the other hand, if you have never found the need to learn anything from that list of topics, you are probably using C/C++ in a domain where it is ripe for replacement.