[sofixa]

It went away when not having JS enabled stop being a regular thing ( what, 2010? At the latest!). Before that there were users with very old browsers, or asinine corporate "security" policies that didn't have JS; nowadays it's only luddites longing for HTML-only websites ( we must have lived in different times because those were just terrible to read, especially if you had a nonstandard (for the developer) screen size), aka a negligible amount of internet users. It's a pretty safe bet to not even test what happens when JS is enabled.

[kkfx]

I politely disagree: today usage of js should be considered criminal not only because of privacy but because of IT {e,in}volution at a whole. In the past all desktop OSes are document-based and work in peer to peer networks (starting from Xerox workstations) since them we only have made crap to copycat those historical systems in buggy, limited and limiting ways just to avoid leaving end users any control of the system they use.

Such move is harmful for the society and must end before it's too late. We must came back to classic desktop computing and punishing all evolution that try to lock users. Modern web(cr)apps fall in this very category.

It's very asinine for instance forcing people's on crappy bloated banking portals instead of agree around a common and standard API (like SEPA OpenBank) leaving users using their favorite local app where all transactions are locally stored, digitally signed by the bank so source of truth in user hand, always available, with as many banks as users want under a common user-chosen UI. No need for crappy monsters WebVM, no need for gazillion of resources just to keep pushing around garbage mostly used for surveillance. The same apply to taxes and pretty anything else.

Personally I like reading post with Firefox reader just to avoid being distracted by the crap added to most websites, if a website does not render in Reader or without js I simply avoid it.

[JohnFen]

Which is very poor engineering.

It also walls an increasing amount of the web off from those of us who reject JS because of the security risks it brings.

[baash05]

It walls an increasing amount of the web off from a really small and ever decreasing amount of people.

I'd actually say it's good engineering.

If I engineer a small gas can (for filling my lawn mower) I can build one that holds a gallon, or one that holds 5 gallons. Now 2% of the population that owns lawn mowers have massive yards and riding mowers. So which one do I engineer? Which do I build. I build for the 98%

Optimist says cup is half full

Pessimist says cup is half empty

Engineer says cup is twice the size it has to be.

The reality. Building for the 2% just isn't an effective use of resources.

-- Oh oh.. I got a better one..

-- How many bridges in your home town have allowance for horses. Are all the bridge builders bad engineers?

[IncRnd]

The way software development is generally practiced is not "software engineering" but "MVP development", which has nothing to do with anything but getting a piece of the pie. If a particular user doesn't fall into the biggest slice of that pie, the MVP developers don't care.

[emj]

I've always felt that it's easier to handle older browsers with, if JS is an optional feature. Luddites must be the wrong word here, since it's mostly highly technical people that disable JS and cookies, old farts doesn't work either since there are more young people around me that does it.