> Until recently, though, there has been an impedance mismatch between your application code that does the initial render on the server, and any separate-but-ti

> Until recently, though, there has been an impedance mismatch between your application code that does the initial render on the server, and any separate-but-tightly-coupled logic that renders further interactions and updates in the browser. Of course, like all sensible users I absolutely despise JavaScript and can’t stand when web devs decide to burn my battery for no reason. But, I wonder if we’re anywhere near pushing through at this point? Perhaps a framework could be invented that detects that the user has disabled JavaScript, and actually do all the JavaScript rendering server-side? I guess at that point web devs could script to their hearts content and their employers will bear the cost power cost of dynamically generating a bunch of stuff. (Hopefully the incentive change there will cause them to be more prudent, but if not I guess I don’t really care that much).