Re:Web Components Eliminate JavaScript Framework Lock-In
by troupo on Monday November 27, 2023 @03:45PM
(#38438010)
> I'd really like something that worked easily with SSR and client-side
Then you should skip Web Components :)
Re:Web Components Eliminate JavaScript Framework Lock-In
by robin_reala on Monday November 27, 2023 @03:53PM
(#38438109)
For sure. SSR is one thing that React has done well, and that Web Components don’t have a great story for.
Re:Web Components Eliminate JavaScript Framework Lock-In
by pseudosavant on Monday November 27, 2023 @04:01PM
(#38438227)
I'm pretty sure that just shipping the HTML works. The nice thing if I use web components is that I can just have my backend create HTML that uses those components. I can create elements whatever way I want on the backend or the front-end so long as it is HTML.
Re:Web Components Eliminate JavaScript Framework Lock-In
by robin_reala on Monday November 27, 2023 @04:23PM
(#38438531)
Yes, if you stick to custom elements. If you want shadow dom encapsulation then you’ll need to wait for declarative shadow dom to turn up in all browsers.
In retrospect, I think I avoided web components because of Google and their aggressive dev relations pushing Polymer. It felt so one-sided that it didn't seem like a web standard. It felt more like a Google "standard" like NaCL. Having to ship Polymer to support non-Google browsers felt even more heavy weight than React.