Yeah, iSnow made the same point, but it doesn't scan. "Boss, I can make it work w/o JS but it will cost more..." Huh? Doesn't that sound just like what an unprofessional developer would say?

The fact that so many popular JS frameworks don't do the right thing is part of the JS abuse in my opinion (same goes for accessibility.) Lazy developers wrote half-assed frameworks and other lazy developers chose to use them and then people start to believe that adding JS somehow makes it hard or expensive to do without JS when really they are just doing it wrong in the first place.

> when it's such a small minority of users.

The population of the US is just under 330M, so if, say, 0.5% can't or won't run JS to interact with taxpayer-funded government services that's about 1.5M people. Those folks (of whom I am one) should not be disenfranchised, so to speak, because the gov hired unprofessional developers. The government shouldn't do that, and they certainly shouldn't try to tell me that I'm some out-of-date digital neanderthal for caring enough about web insecurity to disable JS, eh? Lousy devs (as demonstrated by the fact that they can't provide a non-JS web experience/fallbacks at an affordable rate) are precisely the ones the JS code of whom I have no wish to run, and I certainly don't want my tax dollars going to pay them to screw me out of access to the service also paid for by my tax dollars.

> choose between spending their limited departmental resources on an extremely small minority, or the greater userbase as a whole.

Or they could use tech that works for everybody automatically for the same cost, eh?