But today's complex computer systems depend on hundreds of thousands of interfaces, and those interfaces are depended on by millions of organizations. Their business model inhibits standardization, instead of aiding it.
The problem is: the time when people learn most about programming is as students when they have too much time and hardly any money.
WHATWG, IETF, W3C. Not that each doesn't have other issues, but charging through the nose for standards isn't one of them.
It takes a special kind of singlemindedness to look at modern web standards and the open source WebKit ecosystem, dismiss their wild, outsized success as a tire fire, and call for more corporate exclusivity as the solution.
As an example, C++, also an ISO standard, has notoriously few full implementations, and as a result C++ is largely defined by "what GCC/Clang accept" in practice.
A proper standard needs to be free (both as in speech and beer), otherwise it needs investment to see that a implementation meets the standard (which in itself goes against the idea of having standards) or to modify it to propose improvements.
The work of developing standards can be done by people/companies who benefit from the standard, either financially or via other ways and those people/companies have their motivations to work on it.