[Fair assessment?]
Current downsides of Web Components (that will eventually go away):
1. You still need a polyfill on Safari (last I checked).
2. Limited support for Declarative Shadowed DOM (needed so that SSR content works without JS): https://caniuse.com/declarative-shadow-dom
Depending on the framework, using both Web Components and SSR may also be tricky (partly depends on #2). I haven’t investigated that yet, but I’d also expect it to improve over time.
@rauschma that's a fair assessment of #WebComponets. I would be remiss in pointing out that you don't _have_ to use declarative Shadow DOM. It's very possible to ship Web Components today without polyfills if you chose to be a bit more selective with the standards you use.
@mcneely Got it. I only stated that you need DSD so that SSR works without JS. True?
@rauschma sorry missed that part of your statement.
That is my understanding but I've never used DSD. It was too new of a feature to be used at my last job where everything was Web Components. I think that for them to really hit a sweet spot for developers it's probably needed.
I believe that enhance.dev is iterating around this specifically with the way they render on the server but I'm not sure exactly how they do it.
@mcneely For many apps it probably doesn’t matter, but as I’m currently working on a static site generator (whose output must work without JS), I noticed this limitation.