Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lit: a library for building fast, lightweight web components

lit.dev

Post reply on HN
Print view View original

41–50 of 180 posts

Re: Lit: a library for building fast, lightweight web components

#41

Post by Muromec »

I had lit in a project at work and not having to deal with it anymore is just great. We already have another heavier component framework to do the actual application stuff anyway, so having two just because somebody wanted to optimize their resume was such a drag.

It all looked nice in theory, but one thing shadow DOM makes worse is A11y, because element ids are now scoped and all the missing describe-by, label-for for things that should link to other side of the fence are a massive pain in the ass.

Big part of it is just skill issue on our part of course.

Re: Lit: a library for building fast, lightweight web components

#42

Post by jfagnani »

iammrpayments wrote: post #39
jfagnani wrote: post #14

Lit maintainer here. I should be going to bed, but I'll answer any questions if people have any! Not sure why Lit showed up on the front page tonight :)

Are properties reactive? Can I reassign name in the example by using document.querySelector?

Yes!

Re: Lit: a library for building fast, lightweight web components

#43

Post by jfagnani »

mkleczek wrote: post #40
jfagnani wrote: post #14

Lit maintainer here. I should be going to bed, but I'll answer any questions if people have any! Not sure why Lit showed up on the front page tonight :)

Thanks for your great work. I can't find clear information about how re-rendering and stateful third-party components interact. Let's say I have a stateful data table web component that I use in the template. Is it going to be re-created every time the template is re-rendered (loosing its internal state)?

Thanks!

Elements are kept stable as long as the template containing them is rendered.

The template docs try to get this across by saying that Lit "re-render only the parts of template that have changed." Maybe that needs more detail.

There are details here: https://github.com/lit/lit/blob/main/dev-docs/design/how-lit...

Re: Lit: a library for building fast, lightweight web components

#44

Post by afavour »

troupo wrote: post #9

The evolution of lit is fascinating to watch because it's built and promoted by people with rather visible and public dislike of everything React. And yet, it's already turned into React-lite. - Custom HTML-like syntax - Custom Javascript rules // valid JS, invalid lit const tagName= "a"; ` Some link ` - Custom rules for special functions. // classMap looks like a regular JS function, but it's not. // Both of these w…

I’m not one of those people but I don’t see an inherent conflict in what you’re saying. My #1 criticism of React is its size and monoculture, so a React-lite alternative sounds intriguing to me. Much like Preact, which I’ve used a ton.

Re: Lit: a library for building fast, lightweight web components

#45

Post by jfagnani »

o_m wrote: post #30

I don't see the need for Lit anymore. Lately I have just been raw dogging web components without any libraries. Having a nice templating system like JSX on the server makes it a breeze. Part of using web components, for me, is that it is just javascript. There is no upgrades or deprecations to think about. Of course those things still exist on the server though, but it is easier to maintain it there.

The great thing about web components is that you can build them however works best for you.

Native web component APIs don't have the DX that many people expect though, because they are so low-level. Lit provides just that declarative reactivity on top.

Re: Lit: a library for building fast, lightweight web components

#46

Post by mdhb »

troupo wrote: post #19
jfagnani wrote: post #13

Earlier quoted context omitted.

You have a very large axe to grind against web components and Lit, and you show up just about everywhere to make the same comments, but I'll play along anyway: Yes, Lit templates give some special meaning to attribute names with a few prefixes. No, it's not "HTML-like". It's valid HTML. Not that it matters much. You bring this up all the time but I'm not sure what the actual criticism is. Developers seem to understan…

> You have a very large axe to grind against web components and Lit Yes, yes I do. Because Web Components are almost 15 years now, and they still struggle with the most basic of things. How's that abandoned roadmap going? https://w3c.github.io/webcomponents-cg/2022.html > No, there are no custom JavaScript rules. Templates have some rules. That is "here are regular JS functions. However, you cannot use them as regula…

Take this as some constructive feedback that you really come across as a miserable bastard to everyone reading your comments.

Re: Lit: a library for building fast, lightweight web components

#47

Post by mulhoon »

Working with a large Vue 3 project and wanting to share some of our components as re-usable web components for other sites to embed...

What would be the benefit of rebuilding these components in Lit over using Vue to build them?

https://vuejs.org/guide/extras/web-components#building-custo...

Re: Lit: a library for building fast, lightweight web components

#48

Post by iamsaitam »

kubb wrote: post #15

For the frontend work that I did, Lit was a godsend. It really helps you build components and apps without getting in the way. In comparison, Angular is a monster, and React is designed for the old browser capabilities, and is now staying around by inertia, not by inherent quality.

"React is designed for the old browser capabilities and is now staying around by inertia, not by inherent quality." this makes me feel old and I guess React is famous for supporting Internet Explorer /s
Post reply on HN