As I said, this isn't just a problem for no-JS browsers, it's also a problem for people with slow Internet connections. They might be able to load the HTML and

As I said, this isn't just a problem for no-JS browsers, it's also a problem for people with slow Internet connections. They might be able to load the HTML and CSS reasonably fast, but then they'll have to sit around waiting while megabytes of JS is downloaded and then executed before they can finally read the article. I'm not asking developers to do extra work to accommodate no-JS browsers, I'm asking them to not do extra work to deliberately prevent sites from working without JS. The page would have worked perfectly if the author had not done extra work to add a useless loading screen. I'm asking developers to do less work, not more.