[KenPainter]

For all practical purposes the various component systems (react, angular, vuejs, svelte) all have the same abstractions, and they are quite powerful. The front end wars are over, the component abstraction won.

But the browser native solution, "web components" proper, we have found do not have the same capabilities.

This conclusion comes from a team I lead that produces components for internal consumption by our product teams. We generate Angular and React components from our own DSL. When we considered creating web components we found they were limited in the manipulation of child content (in angular terms: projected content). There were numerous other nits that kept coming up that I don't remember.

It seems to me the web component idea itself is a zombie. This may be overstating the case because my perspective is about supporting hundreds of teams, but I sense it has no future.

[postalrat]

So your suggestion is to create some sort of DSL then publish your components in Angular, React, and every other library that's requested?

[KenPainter]

No. Just offering the perspective from a place of having done so myself, that web components are not as capable as the big 4 of react, angular, vuejs and svelte. I'd stick with one of those four for a single project,