To be honest, it would be much better for someone to just fork the language and start a new team rather than transforming the existing leadership.<p>I really don’t think design-by-committee is a good method to create a language. There’s a significant gap between spec writers, compiler developers, and end users when it comes to C++. I think this can be alleviated if the language designers work closely with the compiler devs as one team, while listening to user pain points directly - which is why I think Rust had success in a relatively short amount of time.
In this post, there seemingly a lot of focus on process, infrastructure (for the committee) and ideological issues. Instead, I would love to see a focus on technical competency, speed, and addressing customer requirements (for developers and companies).