They are probably unaware of how much of a minimalist rob is. Even before ai, he was designing his clis so that unless there is an error, no information needs to be returned. No news is good news. Unix.
So ai generating unnecessary noise that consumes energy for nothing?? Must be maddening.

Oh ok I didn't know.

That doesn't seem like the fault of standardization 😅
It seems it is the fault of using a premature implementation as a de facto standard.

Unless I am mistaken?

that's not SPAs, it's the livewire/htmx model.

chaotic

Nani?!!! letters?!!! Dan is moving to medieval Japan 😂

I would also not add event listeners binding. And be careful about template scoping.

That's going to be tough. As someone who has implemented such a thing, it is tied to the reactivity system you use.
So unless there are reactivity primitives added to ES (which I am not sure would be wise), it is more likely that it should be a bespoke implementation. But it is totally doable today.

some people choose to read offsetWidth for instance to force a flush.
Needed when switching something away from display:none and trying to focus it, programmatically.

at times may require to flush the changes immediately. very rare but I wish that the side effects would be immediately visible, conceptually.

It's the same kind of issue that the browser has too when scheduling renders in vanilla js.

Have the same issue in the framework I am building. Basically with reactivity, I have made normal assignments side-effectful. Except the scheduling of the side effects that are not a derived/computed puts them in a microqueue that flushes by next tick.
In the general case not an issue.
But...