3 ms·
> I suspect that the author (authors?) wouldn't disagree at all with "use Rust when possible, Carbon when you can't" That is in fact explicitly stated on the C
by kllrnohj 4y ago
> I suspect that the author (authors?) wouldn't disagree at all with "use Rust when possible, Carbon when you can't"
That is in fact explicitly stated on the Carbon introduction:
"Existing modern languages already provide an excellent developer experience: Go, Swift, Kotlin, Rust, and many more. Developers that can use one of these existing languages should."
- nextaccountic 4y agoAlso on their FAQ https://github.com/carbon-language/carbon-lang/blob/trunk/docs/project/faq.md#if-you-can-use-rust-ignore-carbon= https://github.com/carbon-language/carbon-lang/blob/trunk/do... > If you can use Rust, ignore Carbon > If you want to use Rust, and it is technically and economically viable for your project, you should use Rust. In fact, if you can use Rust or any other established programming language, you should. Carbon is for organizations and projects that heavily depend on C++; for example, projects that have a lot of C++ code or use many third-party C++ libraries.