Now the latest Web framework trend is to do start headless browsers to do server side rendering.
And yet, every time that the number of standards is reduced, it is by this same process.
So, yes, it is the one way to do it. And yes, more often than more, it fails completely. So, let me ask you, what is the point of complaining that somebody is going through that?
Is it? I'd say it's usually rather because:
(a) Some of the competing standards wither and we get rid of them.
(b) Some standard emerges as the winning one and is adopted by everybody.
But very rarely by the addition of a new standard.
And for competing standards to wither, there somebody must have created the other standards too.
I wrote "emerges as winner". Not "emerges period".
Which does not require creating a NEW standard on top of existing ones (N+1), since an already existing standard (of N) can emerge as the winner.
And more often than not, they are right.
In this particular case Web Components only solves part of what frameworks do, and solves it badly. As badly as CSS solved the layout problem the last 2 decades.
I wouldn't mind a nice Web Components solution, but the current design reminds me of the over-engineering of things like Swing and JSF.