News for hackers. Stuff that matters.
Re:A Guide to Porting C/C++ to Rust by quickben on Sunday January 29, 2017 @10:10AM (#13514411)
Nothing. Unless you think rust will become the next c++, and the world will move to it en masse, in which case people still won't rewrite most of the old libraries to it.

At best people can hope that somebody comes up with a neat import system of c++ namespaces, a rock solid debugger and a fluid ide.

Rust will be like Go. Both pushed by corporations, and probably follow the fate of cobol, if history is to be asked.

Re:A Guide to Porting C/C++ to Rust by bluejekyll on Sunday January 29, 2017 @12:30PM (#13515301)
> Rust will be like Go.

Perhaps in adoption, but Rust has a huge feature over Go, which is that it can be integrated into existing codebases through FFI conventions, such that you can slowly incorporate Rust in safety critical areas (as an initial starting point).

Re:A Guide to Porting C/C++ to Rust by moomin on Sunday January 29, 2017 @10:18AM (#13514445)
Since COBOL is the longest actively used language I wouldn't say that was so bad.
Re:A Guide to Porting C/C++ to Rust by quickben on Sunday January 29, 2017 @10:43AM (#13514572)
If anything it was good for the overall good of our ecosystem. People coded it, used it, built with it. We all are in a better place knowledge and experience wise. New languages generally are good.