SoylentNews is people
SoylentNews
from the Obfuscated-Rust-Competition-doesn't-sound-right dept.
In spite of my status and obvious bias as co-creator of D, I'll do my best to answer candidly; I follow Go and Rust, and I also definitely know where D's dirty laundry is. I'd encourage people with similar positions in the Rust and Go communities to share their honest opinion as well. So here goes.
First off, C++ needs to be somewhere in the question. Whether it's to be replaced alongside C, or be one of the candidates that's supposed to replace C, the C++ language is a key part of the equation. It's the closest language to C and the obvious step up from it. Given C++'s age, I'll assume in the following that the question also puts C++ alongside with C as a target for replacement.
Each language has a number of fundamental advantages (I call them "10x advantages" because they are qualitatively in a different league compared to at least certain baselines) and a number of challenges. The future of these languages, and their success in supplanting C, depends on how they can use their 10x advantages strategically, and how they overcome their challenges.
[Another way to look at this is to ask "What is wrong with C?" and then assess how well these languages solve those problems. -Ed.]
(Score: 1, Insightful) by Anonymous Coward on Friday November 13 2015, @02:31PM
So, for example, if you put C in front of a room full of Python programmers, chances are basically 100% that they'll be able to understand what's going on.
You're overestimating the abilities of most programmers. Lots of them know only their toy languages and don't know what's happening in the background. Even something like C would confuse them, let alone assembly.
but that turned out not to be a silver bullet for those situations where objects aren't a great metaphor to be using.
So don't use them. It sure is nice that C++ gives you options.