But you have to implement this "extra functionality" already. Or, how are you dealing with situations where your JavaScript fails to reach your user's browser? How are you dealing with situations where the JavaScript arrives in the browser but doesn't execute?

This "extra functionality" is the same "extra functionality" as having a safety cage designed and implemented in a car. Sure, it's just extra functionality that most people will never ever use. Hopefully. Touch wood.

If it doesn't work without JS, is it going to work in a screen reader? Should developers have to implement extra functionality for the < 1% of people who are blind?

Nobody is forcing developers to give a damn about accessibility, but it's a bit sad that so many have thrown graceful degradation out the window.

That depends entirely on your site and audience.

Although some counter by saying that you shouldn't need to provide wheelchair ramps for the < 1% of people who are unable to use stairs.

Sometimes it's not just about ROI.

But go back to HN for a moment, there's not really a good way to insert new threaded comments in realtime, you pretty much need a refresh. So the no-js method is about perfect.

>But would always require a complete page reload.

So? A complete HN page is smaller than JQuery.