Earlier quoted context omitted.
Ah, I see the point about SSR. Yes, frameworks like React and Vue make it less obvious how to do non-framework SSR. However, they don't make it impossible. You can have React and Vue render on an individual element and not the whole document. The HTMLElement part of web components are actually a decent way to do that. You can make a thin wrapper HTMLElement that runs createRoot. https://react.dev/reference/react-dom/…
Do you know what SSR is?
The Case for Web Components: A Simpler, Framework-Free Future for the Web
21–23 of 23 posts
[deleted]
Re: The Case for Web Components: A Simpler, Framework-Free Future for the Web
#22Been hearing the case for web components for a very long time. Are there any implemented well? Last I looked at shoelace/web awesome, using a single component brought in 40k+ of JS
Shoelace is excellent, in my experience! Well document, accessible, and a large selection of components. To solve the issue you mention, you can cherry-pick the imports [1], which imports only the specific component you need.
[1]: https://shoelace.style/getting-started/installation#cherry-p...
Re: The Case for Web Components: A Simpler, Framework-Free Future for the Web
#23This seems to be a pretty low-effort post without any real substantive details. I'd much rather see discussion of the "Parallel Evolution of React and Web Components" article that got posted earlier today. I don't agree with that author's strong stance against React, but it's at least a well-written post with substantial thought and significant technical detail: - https://news.ycombinator.com/item?id=41790499 or thes…
It seems like it was written by ChatGPT.
96.3% confidence score that this post was written by/edited with ChatGPT 4-o.