Thread by @wycats

If a framework doesn't support web components well, it means they don't support HTML well.

A web component is an HTML tag and a bunch of attributes, which is why they're so great. If that doesn't "just work" it means there are a ton of invisible special cases in HTML handling.

It probably means SVG support is hacked in and doesn't work that well, and that there are frequent gotchas in normal HTML generation.

This was already a bad idea before, but people managed to convince themselves that it was ok if you hand-coded solutions for all of the built-in components.

Again, bad idea that inflicts papercuts on developers over and over.

But when custom elements are in the mix, the only thing to do is to have good, uncaveated HTML support that takes HTML syntax and produces equivalent tags-with-attributes.

This whole topic has been the source of massive ecosystem confusion, but the chickens are coming home to roost with web components.

Web frameworks produce HTML and trying to treat HTML like a series of special cases imposes pointless pain on people for no reason.