People are downvoting you, but I totally agree. Stop requiring javascript to let me read text: literally the first thing ever put on the world wide web. Fancy your page up with javascript if you must, but let me choose to consume the text how I want.
Since you are new here, I'll explain why I and others most likely have downvoted his comment, and why it's acceptable to do so, regardless of whether I agree with the sentiment or not: it's off-topic, and adds nothing to the discussion in the linked to article. Most importantly, it's essentially complaining that the content is inappropriate.
I have no idea why the blog is fetching a Markdown file via JavaScript from GitHub and then using JavaScript to render it... but at least you get the nice "doge" if you don't have JavaScript enabled.
I beg to differ. A vocal minority of users who are aware of the JS dependency speak up for the unknown subset of users who can't read the page due to an error and don't care enough to investigate.
If a page starts to lag when I'm scrolling on a phone, it isn't worth the CPU cycles, battery life or my frustration to continue using it.
It doesn't even load anything from another domain, so what's the problem with it? That link says that it's "dead to history" which has nothing to do with reading it right now.
The link you gave requires knowledge of the Github API. The original HN link does not give useful page content when cURL'd, and is the same stuff seen when you view source in any browser:
From a decision standpoint, wouldn't sites that require JS to render content be more important to read now, while they're correctly rendering? It's transient information that may not exist tomorrow -- why would you choose to not read it?
Because presumably you're "NR" as a method of punishing the author of the page, but surely you can't think this act is in any way consequential.