Yeah no shit.
Yeah no shit.
But when most of the articles submitted here don't work without JavaScript, this comment seems really irrelevant.
I guess my question would be why does something so benign and common aggravate you so much? That feels like an exhausting way to live.
Most importantly, enabling JS makes it much easier to spy on users, so I automatically assume that the website tries to spy on my and feel attacked.
I agree it's not healthy, and I didn't care about privacy that much in the past. I guess this may be caused by my work experience.
From what I can see, they're doing so codeblocks have proper highlighting but also can be copied & pasted. It's a reasonable choice.
They're not lazy. They even have long, accurate alt tag descriptions for all their images.
If I would guess, they have an inherent desire to see their work viewed in exactly the way it was intended, so they deliberately refuse progressive enhancement when it's a matter of reader choice. The visually impaired who have no choice are accommodated. Anti-JS readers are not.
Because that doesn't include writing JS, that's a separate step.
Presumably this is easier than a non js solution or they couldn’t find one.
- The page will load noticeably faster (and likely be faster in a number of other ways).
- The semantics are more predictable (buttons, links, scrolling, text selection, find-in-page, etc. all behave the same as on other websites).
- The page will work in Tor Browser's "maximum security" setting.
- The page is more likely to work better in screen readers or with other less-commonly used web browsing tools.
- The page is more likely to work in older browser versions.
- It used to be that a JS-free page had lighter CPU usage, though newer CSS features and browser setTimeout/setInterval throttling have changed the balance somewhat.
- The page does not require running untrusted/proprietary code on your computer (the browser sandbox is a small comfort).