It must be frustrating to propose a bunch of ideas, cultivate and advocate for them, only to never see them acknowledged or accepted by the standards committee over the course of years.
That being said - let's get real about this. Simply coming up with a bunch of ideas for improvements is not enough. Neither is being vocal about it on Twitter, or giving talks at a convention. Gaining the community's support and acknowledgment is key here.
That you feel something is an "improvement" doesn't mean others see it that way. Same for "faults" and "imperfections". This isn't the community's fault, or Bjarne's.
This is the reality of working in a team. On a language used by millions of engineers around the world, which powers every facet of our modern society.
Especially for committee work, it's quite clear once you go there that what matters is being sponsored to attend regularly and build up relationships so that you can get experienced people on your side.
People on the committee are not sufficiently good to just accept a proposition based on technical merit alone. The whole thing needs to be made accessible and easy to digest, and preferably integrate well in what others want to do.
It's political work, which is tedious and frustrating. Some people are good at this (especially if they can figure out a way to integrate that into their career), but for most people, it's just a waste of time and effort.
That being said - let's get real about this. Simply coming up with a bunch of ideas for improvements is not enough. Neither is being vocal about it on Twitter, or giving talks at a convention. Gaining the community's support and acknowledgment is key here.
That you feel something is an "improvement" doesn't mean others see it that way. Same for "faults" and "imperfections". This isn't the community's fault, or Bjarne's.
This is the reality of working in a team. On a language used by millions of engineers around the world, which powers every facet of our modern society.