Sorry, not in the ecosystem (clearly).

Why not? Just curious.

In fairness this is as opposed to Go? Swift? Rust? Java? C#?

Then C and C++ are defacto controlled by private companies: Google+Apple do pretty much all the clang development, MS does MSVC - if they choose not to implement a feature that’s approved, or implement one that isn’t, that is the de facto standard.

You can argue it would require all three to agree on something, but that’s still essentially making WG21 somewhat irrelevant.

I prefer a fast evolution when necessary to a slow committee process. I don't see any drawbacks, unless your the type that prefers to build consensus before moving forward

It hasn't been an issue at all for Go. As long as all the source is public, I don't see an issue using a large, overvalued tech monopoly for advancing technology.

At some point between here and like, shipping a language design and working prototype, the stated intent is to build a Foundation like for several other modern projects and then assign everything to the Foundation.

""We are planning to create an open source foundation and transfer all Carbon-related rights to it; our goal is for the foundation setup to be similar to other open source projects, such as LLVM or Kubernetes.""

I doubt it'll make much headway, though I'll admit this is the direction they should've started Rust on. Imagine if all this post-C++ effort was put into just making a functional package manager that'd be an actual game changer imo.