> Yeah, because yelling against Web Components in every forum thread is so much more productive.
I'm not yelling. I'm pointing out facts.
> regardless if they are at their foundation or not.
So why are they not used as a foundation? Why are they used at best as a second class citizen? Why is it these frameworks don't produce web components by default?
> Who is actually being ignored here?
Framework authors, who have been pointing out the very many deficiencies and shortcomings for years. Most developers who need things like scoped CSS and open-ui.org more than fifteen hundred new standards, each requiring JS to work, barely.
I only see React framework authors ignoring Web Components.
Angular and Vue framework authors considered them good enough to spend development resources on adding support for Web Components, they didn't do it for fun and glory.
The absolute vast majority of new frameworks don't use web components as the foundation.
Perhaps instead of burying their heads in the sand people pushing web components would should finally start asking why?