It's less "anti Javascript" and more against "it's a great idea to base the entire web around loading completely unverifiable and uncontrolled executable code from anywhere in the universe."
Javascript is a reasonably nice language for what it does, and if it was all still mostly inline or browser managed packages or whatever the modern ecosystem would likely be significantly less of a user-hostile dumpster fire.
Like millions of others, this site looks great in a text-only browser that has no Javascript support.^1 If automatically running other peoples' Javascript or some other "feature" of a popular browser^2 is preventing someone from viewing the text, and the only way to avoid this annoyance is to disable the feature, then the problem is not necessary the feature, but how the feature is being used. People who disable or avoid the feature are not necessary anti-[feature]. They are trying to avoid the effects of how that feature is being used by web developers.
Rendering the primary text content and being able to collapse comments are not on the same level of functionality.
(Though for this particular website, I can see the text just fine with JS disabled in firefox, so I'm not sure why it doesn't work for CaliforniaKarl.)