https://github.com/pflanze/de-elm
(Edit: here's a copy of the content of the linked page: https://github.com/pflanze/de-elm/blob/master/examples/annou... . Tell me if you don't like this and I'll remove it again.)
https://github.com/pflanze/de-elm
(Edit: here's a copy of the content of the linked page: https://github.com/pflanze/de-elm/blob/master/examples/annou... . Tell me if you don't like this and I'll remove it again.)
So, there's a practical point to this, which is that I wanted to read the page, and a mixed practical/political point which is that I don't want to enable JavaScript if I don't absolutely have to. So I sat down and figured out what can be done...
I'm sure this will cease to be useful at some point, but for the moment, I find that some of the time, running the URL in question through Google Cache produces a useful view.
Of course, Google properties themselves increasingly insist upon JS, even for basic "read-only" views. At least I have some confidence that Google is performing some measure of vetting their own JS against particularly the security problems that most concern me.
Here's the OP URL, via Google Cache:
http://webcache.googleusercontent.com/search?q=cache:http%3A...