Ask HN: What is preventing rust from replacing c/c++?

Re:Ask HN: What is preventing rust from replacing c/c++? by twobyfour on Monday July 17, 2017 @07:00PM (#14792996)

Inertia. You don't rewrite an existing codebase unless the current one is simply not capable of doing what you need it to. And there are a lot of existing codebases in C and C++.

[ Parent | on HN ]

Re:Ask HN: What is preventing rust from replacing c/c++? by AstralStorm on Tuesday July 18, 2017 @12:43PM (#14797979)

Even when you do rewrite, there has to be a clear benefit. Rust does not offer a clear one.

(No, reducing amount of bugs does not do anything when pitted against well tested mature software that already exists.)

[ Parent | on HN ]

Re:Ask HN: What is preventing rust from replacing c/c++? by mmstick on Thursday July 20, 2017 @02:47AM (#14810484)

Rust does much more than reducing bugs. It is able to reduce memory consumption, decrease the required amount of CPU cycles, and increase maintainability / adaptability. ADTs aren't a joke, and neither is Cargo, move semantics by default, and the borrow checker / borrowing and ownership mechanics as a whole. Shipping solutions in Rust can be done at record speeds, and integrate with existing software. Rust is wildly successful, and there's no way of stopping it.

[ Parent | on HN ]