This is the most hilarious JS fail I've ever seen. The entire article renders properly, all the text and styling, then the entire screen is replaced by
"Application error: a client-side exception has occurred (see the browser console for more information)."
It's easy enough to fix, just hammer the refresh button to prevent JS from running.
Seems to render perfectly with NoScript blocking all scripts, even with images showing.
It's such a dream state of JavaScript, that people spent countless of time trying to structure these new web applications in a way so that when one function fails for one button or whatever, it doesn't break the entire client-side view, because that'd be horrible.
So what did the frameworks do? Of course wrap the entire application in one big try/catch, that then changes the entire page as soon as there is any error, instead of presenting users with the information that did load properly. Talk about undoing what the platform and language gives you for free...