this is turbo, not turbolinks, so your critique is misplaced. turbo moves state management back to the server, using subregions (turbo frames) for flexible targ

this is turbo, not turbolinks, so your critique is misplaced. turbo moves state management back to the server, using subregions (turbo frames) for flexible targeting and websockets to push (html, not json) state to the client with low latency. in doing so, turbo relegates javascript to its original mission of enhancing the frontend (e.g., stimulus as a companion to turbo), not being the frontend. js is much better at this limited role than being a general-purpose app language. the sooner we can move past the unwieldy patchball that is react (and angular, node, yarn, webpack, endless transpiling/bundling pipelines, etc.), the better.