3 ms·
>You can have code that requires a server or build script with and without web components. You can have code that doesn't require those with and without web com
by ohlanre 2y ago
>You can have code that requires a server or build script with and without web components. You can have code that doesn't require those with and without web components.
Believe it or not, there are other server-side languages apart from node. Without Node, you can't SSR in any of those frameworks, so i don't know how that changes my point
>This is the point that makes the least sense. You can opt out of server-side rendering when using a non-WC framework, and you lose the headaches.
But you miss out on performance... without SSR you are bypassing the html parser and just abusing JS to manipulate the DOM.
> Duplicate of #1. smh
If you insist.
> The API doesn't provide a whole lot. That's why a lot of people are using Lit.
Oh no, a js library.
Your other points aren't even worth responding to.
- benatkin 2y agoAh, 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/client/createRoot https://react.dev/reference/react-dom/client/createRoot
- ohlanre 2y agoDo you know what SSR is?
- deleted 2y ago[deleted]