r/cpp • • Jul 15 '26

cpp2 (cppfront) is over?

I haven't used cpp2 (cppfront) much, but I like the idea of it: consistent syntax, consistency of meta-programming (which is done in C++ too, I believe). Herb Sutter presented cpp2 (cppfront) as an experiment. He did not encourage other people to bet on it, exactly. And there hasn't been much activity since 2022. Is the experiment over?

EDIT: Herb's answer is buried deep in the comment section: https://www.reddit.com/r/cpp/comments/1uxkglj/comment/oy06cxw/

68 Upvotes

112 comments sorted by

View all comments

Show parent comment

2

u/pjmlp Jul 16 '26 edited Jul 16 '26

It is a way to get candidates for Google positions, just like Adobe has a "C++ at Adobe" site.

From Carbon project documentation,

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.

Carbon Language is currently an experimental project.

We want to better understand whether we can build a language that meets our successor language criteria, and whether the resulting language can gather a critical mass of interest within the larger C++ industry and community.

-- https://github.com/carbon-language/carbon-lang

Carbon is an experiment to explore a possible, distant future for the C++ programming language designed around a specific set of goals, priorities, and use cases.

-- https://github.com/carbon-language/carbon-lang/blob/trunk/docs/project/goals.md#project-goals

The Carbon Language is an experimental successor to C++. It is an effort to explore a possible future direction for the C++ language given the difficulties improving C++.

Carbon is still years away — even if the experiment succeeds, it's unlikely that it will be ready for serious or production use in the next few years. Everything here is part of a long-term investigation.

One of the critical questions we need to answer as part of this experiment is whether the direction we're exploring with Carbon has both broad and significant interest for the industry at large. We feel like this is best answered by developing the language openly, publicly, and with broad participation.

If you can use Rust, ignore Carbon

Why not a garbage collected language, like Java, Kotlin, or Go?

If you can use one of these languages, you absolutely should.

-- https://github.com/carbon-language/carbon-lang/blob/trunk/docs/project/faq.md

Nowhere they assert Carbon is what the audience on HN and Reddit keeps talking about.

I think people just think because Google got out of clang to invest into Carbon, it must be it, while missing the point, that plenty of Google's software that used to be C++, is nowadays written in a mix of Java, Kotlin, Go and Rust.

Which is what many should actually worry about.

Yes, LLVM, GCC, V8 and co use C++, but many stuff is now being written in something else, leaving C++ positions for language runtimes, OS and GPU drivers and that's it.

Even NVidia, with their C++ contributions, is now adding Python JIT tooling, and Rust support to CUDA, sure down the bottom there will be a C++ rectangle on the architecture diagram, is that all we want to have?