Post

So lots of hot takes going around about web components. I love em, but I understand the frustrations. Here's my take on the single thing that makes Web Components distinct, for better or worse. jschof.dev/posts/2024/1...

Nice post! I think a couple of claims are a little off though, in particular there are common patterns that make web components easily do things you say they can't in the article...

Like setting properties. This is not a Lit abstraction. Properties are plain JS. You can implement them without any helpers. And you can set them from plain JS too, or from frameworks an libraries like React, Angular, Vue, Lit, Stencil, FAST, etc. Lit just provides a way to do it from templates.

Web components can easily be aware of parents and children. You can fire events to communicate upwards, and you can use events to register children for downward data flow, like the Context community protocol github.com/webcomponent...

In my other posts I gush over the lit context. It's the only reasonable way to share live javascript in a somewhat ergonomic way. Technically though... a provider shouldn't know what should be put in its slots, and there are many that say reaching into your assigned slots is a bad pattern