>>953413
TBF, doing some things clientside is a perfectly fine idea, now that the power of computers has grown so much compared to network speeds (not to mention its even greater necessity for p2p). It's just that:
1. It's difficult or impossible to ignore or customize superfluous formatting in pages, whether done with scripting or not, because the entire structure of the web since the first browser without an integrated WYSIWYG editor has betrayed the "separation of presentation and content" ideal on which all SGML-derived document formats were based.
2. Many things that can be done through native browser features, or even within the HTML/CSS specs themselves, are needlessly reimplemented as scripts. Just like how modern browsers themselves ignore native OS features and external libraries to implement everything from GUI chrome to media decompression in JS/HTML/CSS
3. For desirable features reliant on scripting, there is no capability on most pages to opt out and make the server do it, if you're using a thinner client.
4. Even as lightweight interpreted scripting languages go, JS is a fucking abomination literally thrown together in a week, used solely out of inertia, and has only gotten worse in both user implementation and development culture since then.