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.
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?
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.
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.