News for hackers. Stuff that matters.
Re:Rust 1.0: Scheduling the trains by pcwalton on Friday December 12, 2014 @01:08PM (#8741686)
> All in an effort to cope with the insecure feelings they have because the C programming language and C++ (read: pointers) intimidate them.

You have to know pointers and manual memory management to program in Rust. Rust isn't there to save you from having to learn about pointers. Rust is instead a reaction to the empirically observed fact that nobody [1] has ever written a multi-million-line program with a large team in C or C++ without accidentally making dangerous memory-management-related mistakes, and "just program better" is an approach that has been tried, and failed, again and again and again.

[1]: OK, maybe the Mars rover and the like are counterexamples, but the extreme amount of verification required means that this approach is far too costly to be practical for most software development.

Re:Rust 1.0: Scheduling the trains by throwawayanonon on Friday December 12, 2014 @01:30PM (#8741838)
Rust will not replace C. Rust will merely exist.
Re:Rust 1.0: Scheduling the trains by pcwalton on Friday December 12, 2014 @01:35PM (#8741869)
Sure, Rust's goal isn't to convert all users of C everywhere. C is immortal; that'd be unrealistic. Our goal is indeed to exist alongside C—and to provide a more productive, more secure alternative. :)
Re:Rust 1.0: Scheduling the trains by dragonwriter on Friday December 12, 2014 @01:39PM (#8741880)
> Rust will not replace C.

Rust will replace C in some new development that would have been done in C had Rust not existed, and some existing projects may switch from C to Rust (presumably, by components, rather than as big bang conversions.)

But, sure, its not like C will disappear just because Rust 1.0 exists. But it's not like anyone, ever has argued that to be the case.