Based on what I've read about Carbon, it feels like the project's inevitable path won't be from unsafe to safe Carbon, but rather directly to Rust.
The official documents state the goal is to reuse Rust's ecosystem, not replicate it. Doesn't that mean that Carbon will ultimately just be a stepping stone for the eventual adoption of Rust?
pjmlp•5mo ago
Probably yes, many talk about Carbon without understanding its purpose.
It is an experiment on how to migrate existing C++ code into safer codebases without throwing it away.
Similar in concept as C++ to C, Typescript to JavaScript, Objective-C to C, Swift to Objective-C, Scala and Kotlin to Java, and so on.
With Google themselves as the main customers.
The team themselves are the first to assert that anyone doing greenfield development should rather pick Rust, Go, Swift, Java, Kotlin, C#,... instead.
ninezerobk•5mo ago
The official documents state the goal is to reuse Rust's ecosystem, not replicate it. Doesn't that mean that Carbon will ultimately just be a stepping stone for the eventual adoption of Rust?
pjmlp•5mo ago
It is an experiment on how to migrate existing C++ code into safer codebases without throwing it away.
Similar in concept as C++ to C, Typescript to JavaScript, Objective-C to C, Swift to Objective-C, Scala and Kotlin to Java, and so on.
With Google themselves as the main customers.
The team themselves are the first to assert that anyone doing greenfield development should rather pick Rust, Go, Swift, Java, Kotlin, C#,... instead.