ohlanre

Do you know what SSR is?

It wasn't and I'm not particularly fond of LLMs, that's just how i write.

You can't look up web components on MDN? And if not why it matters, what's my article saying?

>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.

How so?

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'?

Atom was hot garbage, what the hell are you on. Vim is cool but also not an IDE, NeoVim is what you could compare to. Why not VSCode?