This is actually a result of Lit not being a framework. Lit just lets you implement the internals of a web component. Web components don't have a batch state update API, so Lit - not being a framework - has to live within those constraints.

Lit's not a framework. It's an internal implementation detail helper for building components. From the outside, the components are just web components.

I have an old proposal to add lazy registrations, and some Lit prototypes to "split" elements into eager and lazy parts, and there are various wrappers like you describe to notice tag names and load definition modules...

The later is probably the best thing to do for now.

I think frameworks should influence standards more and try to obsolete their current implementation, if not more.

That's one reason I'm working on a native templating API proposal: github.com/justinfagnan...

I use Wireit as the coordinator which means I get to bring my own version of very plain TypeScript. I've seen too much pain with project setups where various tools bring their own version of either typescript, esbuild, etc., and have competing errors. I just don't want anyone but me doing a build.

Web based browser UIs are awesome, and not so rare!

I'm of course partial to the web components ones. Firefox's UI is now built with Lit, and @pfrazee.com built Beaker's UI with Lit before he made this little socials website here 😱

I take them when I can when I'm in SF. They are much better drivers than your average Uber driver.

Even just avoiding drivers who look at their phone or fall asleep is a big step up, but they're quite a bit better than just that.

I hope the cars get better sensor packages for things under the car, but the simple fact is that human-driven cars are supremely dangerous and good self-diving care are so far demonstrably less dangerous. There are still incidents, just fewer.

People bring up the KitKat bodega cat situation: the car stopped for the cat, but the cat ran under the car and stopped under a rear tire. Really unfortunate, but I think a lot of human drivers would have hit the cat too. I know multiple people who've run over their own cats in their driveways!

It's fine to unconditionally oppose self-driving cars. (I think that's wrong, because human drivers are terrible and Waymo's at least are safer.)

But let's have reasonable arguments. A Waymo getting rear ended while sitting in traffic or waiting to make a right does not show that they're unsafe.

That is a wild example to try to pin on Waymo. The Waymo was yielding to a pedestrian while waiting to make a right. The motorcycle rear-ended the Waymo and was then hit by another car, who drove off. And somehow this is the Waymo's fault?

It just kills find too. At least there should be a URL parameter and a button to expand all conversations.

Are you transmitting template results across the worker boundary?

He's not mayor yet. He's fundraising to pay for the costs of the transition until he's sworn in.

Good brain!

I want to do something that sounds similar, which is to SSR, but tag bindings to identify their value in a big graph of data so that you can hydrate the component and pull in its data without hydrating the parents that fed it the data.