Why Does Carbon Development Seem Slow?

[meftunca]

Let’s be honest: when Google announces a "C++ successor," you expect a massive, rapid effort. But observing the development of the Carbon programming language, the pace is concerningly slow.

The promise was clear: a modern, safe, and interoperable language to address C++'s deep flaws. Yet, the current progress feels less like a major industry initiative and more like a low-priority research project.

My question is direct: Why the lack of urgency?

1. Is the C++ Interop Problem Too Big? Is the necessity of perfect compatibility acting as an anchor, slowing down every design decision to a crawl?
2. Is Google Losing Interest? Are the resources (both people and budget) being dramatically scaled back, suggesting a lack of long-term commitment to the project?
3. Is This an Unrealistic Goal? Are we witnessing the inevitable reality that replacing C++—even partially—is simply too monumental a task for this scope?
4. When will we see something concrete and genuinely usable, not just incremental proposals? We need to move beyond foundational architecture and see real features that justify the transition.

We are watching a critical moment for systems programming. If Carbon is the future, it needs to move like it.

Change my mind: What is the critical work happening right now that justifies this glacial speed, and when can the community expect a significant, accelerated push forward?

[danakj]

Sorry none of these assumptions seem correct. Designing a programming language takes time. The work will continue to be incremental in nature as we build, validate, and iterate on the design.