Go is closer to C than C++, and Rust is closer to C++ than C. However, it is D that will be the new C++.
Name:
Anonymous2013-08-29 11:39
Feces is closer to Turd than Shit, and Dung is closer to Shit than Turd. However, it is Poo that will be the new Shit.
Name:
Anonymous2013-08-29 17:40
Give her the D :D
Name:
Anonymous2013-08-30 3:19
C and Rust will both be used, C never dies.
Scala will replace Java in many places, Clojure won't go anywhere. Java, like C, also never dies.
D will eventually replace C++. Only Google will end up using Go.
The rest will just hang around.
ARM won't overtake x86, as x86 is getting better at reducing power usage faster than ARM is getting better at delivering performance. John Carmack believes in x86, and he's a rocket scientist. He knows his shit.
Name:
Anonymous2013-08-30 3:22
x86 will be relevant as long as it maintains the network effect of millions of x86 closed source binaries.
Will Rust be the new C?
Never. No matter how hard you try, you can't replace C.
Clojure will be the new Java?
Clojure is awful, Scala might become the new language for the JVM though. That said, Java itself will never die.
Will Go be the new C++?
No. Sepples is a clusterfucky, awfully design language and Go is a language that rather enforces coding style in its standard than fix some of the core issues.
Will Perl6 be the best thing about Perl?
When it's finished, yes. It never will be.
Will Ruby and FIOC continue their legacy for a few more decades?
Yes. Web monkeys need something to use, as long as it's not PHP, I'm fine with it.
Will Haskell use superior_snake_case instead? I actually like shitCase.
C doesn't die because its just at right sweet spot in the abstraction/performance spectrum.
A language that has more abstraction(lets call it "Blub") makes programming easier but imposes a performance penalty(e.g. overhead/GC) and its abstractions forbid lower-level optimization.
A language that has less abstraction(lets call it "Abacus") requires too much manual labor and its performance advantage is matched by inline assembler of C.
>>17 abstractions forbid lower-level optimization leaky abstractions forbid lower-level optimization. C is not sweet at all, you ought to take care of your structs and loops. For brute performance, Fortran is better than C.