News for hackers. Stuff that matters.
Re:Why C++ Is Not "Back" by acqq on Sunday December 02, 2012 @01:48AM (#4860392)
If you're doing anything serious, you need something that is going to compile even when compiler changes from version to version, unless you plan to write only a few lines, when it doesn't matter which language is used anyway. That's why I don't understand your argument for Rust.

I'd vote for D.

Re:Why C++ Is Not "Back" by pcwalton on Sunday December 02, 2012 @03:25AM (#4860555)
Rust feature freeze is soon. These days we reject probably 90% of the proposals to incompatibly change the language.

There will still be churn, but it's much smaller nowadays; once we hit 1.0 we will be committing to backwards compatibility.

Re:Why C++ Is Not "Back" by Dn_Ab on Sunday December 02, 2012 @04:32AM (#4860689)
I'm also really excited about Rust. What would be unimaginable exciting would be if Rust has any plans for iPhone or Android devices. Preferably without a 10MB runtime and a decent debug story. Elsewise, absent the runtime,F# is the most interesting language closest to fitting that bill.
Re:Why C++ Is Not "Back" by pcwalton on Sunday December 02, 2012 @07:32PM (#4863302)
Rust definitely has Android support planned.
Re:Why C++ Is Not "Back" by eliasmacpherson on Sunday December 02, 2012 @04:11AM (#4860653)
If you look at what's been added and removed from C++ and the C++ STL as of C++11, there are changes required to get formerly valid code to compile under it too. noexcept() as a replacement for throw() in particular. I'm sure Rust has a lot more frequent changes though.
Re:Why C++ Is Not "Back" by hamstergene on Sunday December 02, 2012 @05:53AM (#4860828)
Rust is changing because it's still under development. D had that period too.
Re:Why C++ Is Not "Back" by shawn-butler on Sunday December 02, 2012 @06:23AM (#4860890)
I gave up on D despite all the positives some time ago because of no support for ARM by Digital Mars. I wonder if the situation is improved now with the GDC effort to use GCC 4.7, 4.8 as a backend?
Re:Why C++ Is Not "Back" by pjmlp on Sunday December 02, 2012 @04:15PM (#4862529)
You have support via GDC and LDC.
Re:Why C++ Is Not "Back" by shmerl on Sunday December 02, 2012 @01:57AM (#4860406)
Rust got into more stable state with the last release.
Re:Why C++ Is Not "Back" by pretoriusB on Sunday December 02, 2012 @06:48AM (#4860922)
>If you're doing anything serious, you need something that is going to compile even when compiler changes from version to version, unless you plan to write only a few lines, when it doesn't matter which language is used anyway. That's why I don't understand your argument for Rust.

C changed going to ANSI C, and C++ change a lot from "C with classes" to the first standard. And D, the one you would "vote for"? Wasn't there the whole mess between 2 versions of the language and libraries?

So, why should Rust be any different, considering it's still in design and pre-stable?

When the spec freezes and Rust hits version 1, it would be a fully suitable language for his needs.