22 ms·
Page bloat is one reason, tracking/privacy-invading JS is a pest, but for me at least, my main problem is that most JS is used to break how people want to use t
by PaulRobinson 2y ago
Page bloat is one reason, tracking/privacy-invading JS is a pest, but for me at least, my main problem is that most JS is used to break how people want to use the web.
The web is a document-centric medium. I load a URL, I want to look at the document presented at that page.
Things I likely don't want to do is deal with banners, pop-overs or other code grabbing my attention (if you don't show me a cookie banner you've done the right thing: not use cookies that aren't strictly necessary, thanks!). I probably don't want infinite scroll, "funky" animations or other stuff that tries to break the document medium.
I think the only exception is if I'm looking at a document that wants to use an interactive chart, that's fine. Form validation might be helpful, but do you really need anything other than built-in HTML client-side validation?
- Y_Y 2y agoI like this explanation. If I was trying to be pithy I might rewrite it as something like: JS code is usually run by people I don't necessarily trust, for interests other than my own.