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: 2) by choose another one on Friday November 13 2015, @05:54PM
I remember it, about 0.99pl10 or 11
But I think the goal was not to rewrite using many C++ features but rather to use e.g. C++'s better type checking to find bugs. The attempt failed mostly because of compiler rather than language - in those days g++ was basically s**t, it introduced more bugs than it found and produced significantly slower code, if I remember correctly.
I am pretty sure that early experience with g++ has coloured Linus's view of C++ ever since. The kernel implements C++-like features itself so it has full control over the implementation, possibly because Linus was burned by a poor g++ implementation.