Web components are a complete waste of time and effort at this point. The champions of web components are too invested to admit it, but there are so many problems with the current spec. They haven't learned anything from the current state of the art of building UI for the web.
The web components camp is trying to make them a standard by convincing browser makers to implement them, but this is counter to the way standards have always worked. Usually standards are distilled from usage patterns that are already popular. But web components are not.
There are many examples of successful standards over the years, all of which were derived from an already-popular way of doing things. XMLHttpRequest, querySelector, CSS grids, etc. These were all very popular ways of doing things that became standards.
Today the industry is going crazy over React, and these people are trying to standardize something that literally nobody is using. It's wilful ignorance at this point. Every victory for web components is a loss for the web. We don't need them. It's just part of Google's agenda.
Meanwhile things like declarative programming, one-way data flow, state management, and many other innovations have still (5 years after React) not made their way into the WC model. They have no answer for any of this stuff. There is no innovation in WC. Just old ideas.
It makes me sick because these people are using the standardization process to drive their agenda. Instead of driving standards through adoption, they're trying to drive adoption through standards. It's backwards. Try learning from what the industry is doing, THEN standardize!
React should be built in to the freaking browser. You could easily build declarative equivalents for all the browser's APIs. If you did, you could probably dump the whole DOM API in 10 years because nobody would be using it anymore. They would realize there are better ways.
