> Web components are a browser standard; so anyone thinking about the long haul for their web product would be well advised to think about web components as well.

It doesn't make it

1. a good standard,

2. a requirement, and

3. a viable standard to support

There are countless issues with web components none of which are on any path to solution, they keep valiantly solving issues that only arise from introducing web components in the first place, and there are multiple well-documented and discussed reasons why the absolute vast majority of frameworks (including the new ones) don't use them as their foundation.

> Declarative shadow DOM is an emerging browser standard that is literally compatible with SSR

1. It's only "emerging"

2. As far as I understand, there are still multiple unresolved issues

3. The fact that it's available in Chrome (don't insult us by using the vague Blink-based browsers) means literally nothing. Because Chrome are well known for shipping half-baked Chrome-only non-standards just because they feel like it

(Don't also forget how horrendously bad the whole API is https://twitter.com/WebReflection/status/1526186094232064000)

> The fact that it's available in Chrome (don't insult us by using the vague Blink-based browsers) means literally nothing. Because Chrome are well known for shipping half-baked Chrome-only non-standards just because they feel like it

Great example is Custom Elements V0: they shipped it, forced a Youtube re-write in it (well, in Polymer), literally no one else implemented it, they had to wait ~7 years to remove it from the browser because they had to wait for Youtube to re-write everything again in V1.

Great standards, and a bet on the future, I'm sure.

I wanted to believe it as well, but the fact is their implementation is so clunky and lackluster they are more trouble than they are worth.