>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.
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/client/createRoot
Was it? I confess that I initially downvoted them on principle but came back to remove the downvote after reading the article because it did have strong LLM vibes.
There were lots of turns of phrase that didn't feel natural in a technical blog post but are common in ChatGPT's prose. But honestly the bigger red flag for me was the listicle format, with a numbered 6-point outline fleshed out with a few paragraphs per heading and no transitions or relationships of any kind between sections. It felt like something written in chunks and stitched together afterward, which is a common artifact of a ChatGPT workflow (since it produces small chunks of text at a time rather than whole coherent essays).
I must be missing something. Could you point me to the section(s) in any of those that make the same point I'm trying to? Or, how many more words do I need to use to say 'Web components don't force you to use Node and don't require a build step'?
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.
reply