Feels like throwing the baby out with the bath water.
Feels like throwing the baby out with the bath water.
Looking at HN, which uses js for voting, can be replaced with the olde-school form submission method (at increased page reloads etc), so clearly JS is doing us a favor.
But many sites we visit are consume only (blogs and news) and the rest are generally what we interact with only very infrequently (HN, fb, twitter). It's a rare site that actively needs js (excluding all those react/vue architected sites) that doesn't need human interaction on the first place (eg slack and chat sites that need streaming/comet server responses)
Random thought: Maybe we could investigate a methodology of "jit" for js in response to human interaction. Browsers already do this to limit access to the clipboard functionality. That is, js will run only if the user clicks on a button, etc, but is otherwise dormant (even document.onload would be delayed until first click). Anything else would require permission to run. Of course, this would break the web as it exists now.
The JS here is is an optional enhancement that does the vote in the background. Disable JavaScript and voting still works, it just causes the page to reload. (Aside: it works by using links, but forms so that it’s a POST would be better.)
By conflating our position with "well, just turn your computer off!" you're constructing a strawman.
My issue is with people who complain that a site doesn't work without javascript. All I can think to say is "ya so?".
I don't mean to sound petulant, I really don't.
But it's one of these things that the general market has decided is optimal. Not for build sizes but for building in general.
I think really it comes down to where you draw the line between “document” and “application”. A document should probably work fine without needing to run any additional code. For an application, I don’t think that’s a reasonable request.