As someone who uses all of web components, react and Vue, depending on the project I really feel like to give such aggressive and opinionated takes you should consider doing it in a mature and professional way that goes into the "why" you feel like that.
Have you considered that there are different tools for different problems and that web components have their own space in the wide array of problems?
Because they are a decent fit to a specific set of problems (e.g. authoring components you can embed on different platforms, regardless of the technology they are built with).
I myself, as detailed in another comment, have concerns with web components, and having worked with them extensively, I feel they fall short in several aspects (especially regarding layout control, where they aren't isolated enough due to a series of design choices) but it's manageable.
A problem that I had in two different companies (embedding a set of elements that had to work in very different applications and required the host to know little to nothing) after much analysis was best solved with web components and they did well at that.
The possibility of doing `<script type module>import "yourcomponent.js"</script> <yourcomponent foo="bar"></yourcomponent>` without for us web component authors having to worry about the wide array of different technologies the hosts used (both at compile and runtime) has been in the end the best solution for both us and the consumers.
As Ryan Carniato points out, most of the criticism web components get is that their usage is misunderstood, some of their behavior falls short of their goals, and their name conflates then with framework's components creating further confusion, which are something very different.
The problem with comments like yours is that they add nothing of value to the discussion. We don't know if, when and where did you try to use web components, what hasn't worked for you and why, or if you've ever had the kind of problems where web components would've been a good fit or not.
You end up giving the hopefully wrong impression of an obtuse person lacking the engineering sensibility to understand the context of problems and of their possible solutions.
Wow, your maturity and professionalism are off the charts, and I'll bite.
There are two different kinds of problems: those that nature imposes on us, and those that we create due to our own stupidity and ignorance.
Web components might help you to solve problems created by the latter (and in the process create more problems of the same sort). React, on the other hand, was a true step forwards for how to approach making user interfaces.
Web components are a packaging mechanism for custom HTML tags. If it were just that, fine, but the spec tries to make them into so much more, and this is where the problem and the complexity, and all the shit is. They are not units you should think in when designing your application, because they are not a component framework. They don't solve a single problem I would have when creating an app. If things like web components did not exist, your customers would not run a wide array of different technologies, all doing the same thing in slightly different but equally shitty ways.
Just supply a JavaScript module that creates the component. That's what you would do if there were no web components. And it is more flexible, too.
Now that web components are part of the standard, they might be the more convenient solution for distributing components to heterogeneous environments, and allow for nicer packaging. But the price tag for that slightly nicer packaging is too high, and web components should not exist in the first place.
Also, nobody in their right mind will make web components manually, you will need a higher-level framework from which you can generate web components. And I think one of the creators of such a framework gave you his opinion on this.
To summarise: web components are shit. The world would be a better place without them and the bloat of ill-thought out specs they bring.
