Responsiveness has been fine for a while. Not surprising with the smartphone revolution being nearly 2 decades old by now.

GP asked about reactivity. And that still requires some frameworking, either prebuilt or a lightweight self-written one.

▲

oblio 2 hours ago | parent [-]

What's reactivity in this context? How quickly a website responds? My personal experience is that fast backends with server side rendered HTML and a bit of dynamic sections are in practice MUCH faster than SPAs, 20 years after using Gmail for the first time. Gmail then was fast, 95% of modern SPAs are slow.

▲

bleuarff an hour ago | parent [-]

Reactivity is updating the DOM whenever the underlying data is updated. That's one of the most basic reason for existence of all js frameworks. There's TC39 Signals proposal to bring that natively, but for now as said above the choice is either use a framework or recreate one. It's surprisingly easy nowadays using Proxy.

	▲	0xpgm an hour ago \| parent [-]
		How I've done it is to use some kind of observer pattern, where you register listeners to state changes. Whenever state is updated, the listeners are all called with the updated state and can update the UI and what not based on the new state. I haven't profiled this and compared it to frameworks, but feels adequate for the relatively simple UIs I've done.