News for hackers. Stuff that matters.

A comment on Web Components Eliminate JavaScript Framework Lock-In. Parent comment

Re:Web Components Eliminate JavaScript Framework Lock-In by gitaarik on Tuesday November 28, 2023 @09:19AM (#38445934)
I never used Polymer but as far as I understand it was always an experimental project for the then very young technology of Web Components. And it was a rather opinionated framework also. Lit is just a very lightweight layer on top of the now matured Web Component API. And you are not really dependend on a strong community releasing occational security updates and new features and bugfixes, because it's very small and simple, and it won't really need much new features, because Lit doesn't want to be a opinionated framework, but a simple tool for a single job: rendering a web component.

So because it's small and doesn't need much new features, it's also easy for the community to maintain it. I think not much has changed in the Lit library over the last few years. So it's also easy with upgrading.

[ Parent | on HN ]
Re:Web Components Eliminate JavaScript Framework Lock-In by troupo on Tuesday November 28, 2023 @11:52AM (#38447818)
> as far as I understand it was always an experimental project for the then very young technology of Web Components

So experimental that Google even had a Polymer Conference and was promoting it heavily, like it promotes lit now.

> because Lit doesn't want to be a opinionated framework

For a "non-opinionated" framework it sure does have a lot of opinions: custom DSL, custom directives, custom decorators, custom way of building elements...

[ Parent | on HN ]
Re:Web Components Eliminate JavaScript Framework Lock-In by gitaarik on Tuesday November 28, 2023 @01:28PM (#38449247)
Well, any popular framework has all these things, and most frameworks have a lot more. Lit is really the littlest amount of tools you would want. With less than that, you can just as well directly use the web component APIs, and not use a framework / library at all. I don't know what you imagine would be a less opinionated way without having to chip in on usability.
[ Parent | on HN ]
Re:Web Components Eliminate JavaScript Framework Lock-In by troupo on Tuesday November 28, 2023 @06:32PM (#38453156)
> Lit is really the littlest amount of tools you would want.

- reactivity. Specific to lit

- declarative templates. Specific to lit

- SSR. Specific to lit.

- context. Specific to lit.

- tasks. Specific to lit

- directives. Specific to lit

"littlest amount of tools"

[ Parent | on HN ]
Re:Web Components Eliminate JavaScript Framework Lock-In by gitaarik on Wednesday November 29, 2023 @02:39AM (#38456630)
SSR, context and tasks are all separate packages, not in the Lit core package. The others are very basic functionalily for what you expect from a framework like Lit. It has to do something ultimately :D
[ Parent | on HN ]
Re:Web Components Eliminate JavaScript Framework Lock-In by troupo on Wednesday November 29, 2023 @06:43AM (#38458239)
> SSR, context and tasks are all separate packages, not in the Lit core package.

Splitting hairs

> The others are very basic functionalily for what you expect from a framework like Lit.

Indeed. Framework like Lit. These mental hoops and shenaningans lit defenders have to jump and go through to pretend lit is somehow not a framework and somehow different.

Literally the very first example you get on lit's own page show how invalid all those claims are: https://lit.dev/docs/components/overview/

[ Parent | on HN ]