Lit: a library for building fast, lightweight web components

(lit.dev)

277 points merqurio | 1 comments | 03 Sep 25 06:14 UTC | HN request time: 0.209s | source

Show context

kubb ◴[03 Sep 25 08:11 UTC] No.45113384[source]▶

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.

replies(3): >>45113627 #>>45113773 #>>45114105 #

pmanu ◴[03 Sep 25 09:18 UTC] No.45113773[source]▶

>>45113384 #

That’s also why I really like Aurelia framework. Its component model feels very intuitive, and it embraces standards like custom elements and decorators instead of inventing new patterns. Compared to Angular’s boilerplate or React’s hook gymnastics, Aurelia lets you write less code that looks more like plain JS/HTML. Too bad Aurelia never got the same traction as the big frontend names, because the DX is really solid.

replies(2): >>45114300 #>>45114329 #

1. SebastianKra ◴[03 Sep 25 10:54 UTC] No.45114300[source]▶

>>45113773 #

I thankfully migrated or left all Aurelia projects, but every time someone mentions it, I remember new horror stories.

Its .html temples were shipped unmodified directly to the client. Except they weren't actually html, and sometimes the browser would try to clean them up, breaking the template.

Reactivity was achieved through all kinds of weird mechanisms (eg monkey-patching arrays to watch for mutations). It would frequently resort to polling on every tick or break completely.

DI used TypeScripts experimental decorators, even long after it was clear that it would never become stable.

On the other hand, templates weren't type checked.

↑