In addition to being un-archivable, it's probably also impossible to use with a screen reader.
Edit: ok I don't really know anything about screen readers. I just miss graceful degradation being a priority of web design.
1. Show text content
2. Make the text content look good
3. Allow submission to a comment section
All of those things can be accomplished with some or none javascript. Why make the job harder than necessary? Why screw over screenreaders?
Oh, I see there's a graph there, that probably would use some JS. But why not just hide the graph for noscript users?
I think the mouseover behavior on the graph is cool though so having both (one for javascript people, one for non-JS people) is smart.
It's completely inaccessible to screenreaders, though. I just get "Average Monthly Revenue 2012- 2018 canvas element."
So if it makes the content creators' lives a bit easier, the cost of making the job harder for a small group of end users might be worthwhile.
A ctrl-R only loads about 20kb but still takes about half a second to render.
If the SEO people are to believed, a vast majority of people would click away, what, 5 seconds into that?
No you don't.
I had the same experience as the parent in that I could not read anything unless I enabled a ton of files and once the content became readable it was stuttering all the time while scrolling. In 2019, on a beefy 8 core machine with 32GB of memory.
I virtually always use HN without Javascript. It works great.
Does saying a website doesn't work with JS disabled count as flamebait? This feels like a flamewar to me.
"Eschew flamebait. Don't introduce flamewar topics unless you have something genuinely new to say. Avoid unrelated controversies and generic tangents."
But like... a static blog post? Why bother with JS at all? It seems like creating more work that necessary, bloating downloads, increasing load speed, and for no reason blocking out people with JS disabled (so like, not just people using Firefox with plugins, but people that browse from emacs or whatever... which seems weird, except those are exactly the kind of people that are also technologists building 20k side projects). Also makes accessibility harder than necessary.
The market of people who disable JS is minuscule and very likely not worth the effort to serve.
If you choose to disable a core web technology, then you should expect that many sites will not work for you.
If you choose to disable a core web technology, then you should expect that many users will not work with you.
Is it really too much to ask for a single <NoScript> tag on the home page explaining what the service is and why JS is necessary?
1%. Of all people.
Except... maybe your content is targeting exactly the kind of people to wander around the internet with Javascript disabled, and then they're suddenly a much larger slice of your potential audience. Writing articles on engineering, I imagine, already increases that slice. Anything related to security, I imagine another increase. People that participate in Indie Hacking Projects.... another big slice.
Anyway, why not just make it a part of that big ol blob of meta tags we all copy over to every index.html we write anyway? Including the magical bit of viewport meta to make pages look good on mobile?
One thing that REALLY bugs me, is blocking usage of analytics systems that you cannot access a site without it. Makes the site unusable if the analytics are blocked or otherwise fail to load. I keep JS on, but will be damned if I shut of uBlock.