The first thing that would fail is the ability to login to his own site, which uses Mozilla Persona and requires JavaScript.
To be fair, I'm very much in favour of reducing the amount that the browser does and to send less stuff to the browser.
I'm in favour of Tom's whitelisting approach and I used to believe this was the best way to consume the web. But that was back when most sites still had an idea of gracefully degrading and continuing to function.
Too much stuff breaks now, and I find that a blanket policy no longer works. Instead I user a combination of Disconnect, hosts files http://someonewhocares.org/hosts/zero/ , private/incognito browsing, to block per-site, to prevent bad stuff getting through, and to prevent sites abusing my use of their site (aggressively tracking and marketing).
But... by and large I now leave core JavaScript enabled. As too much breaks.
Some things will break any way (Omniture code that captures an onclick and breaks the anchor by default unless their JS is enabled). I feel that my setup is a pretty good median point though, between blocking junk and having the web remain usable.
The jQuery is so I can progressively enhance the post form. Which you can't see unless you are me.
And the Twitter button doesn't use JavaScript. Very much intentionally.
Also if you think I'm being hypocritical by using JavaScript a tiny amount on my site while also decrying it's overuse, then you've failed at reading comprehension.
Works great. I chose it because (a) I couldn't be arsed to write a username/password setup and (b) using things like Facebook/Twitter requires an API key and I can't be bothered.
That's exactly what I was hoping to hear. I often build one-off web applications (server-side rendered, not JS-filled stuff unless its needed heh) and I hate handling the user/pass setup and flow. Cool to know that Persona will work well for that sort of thing, cheers!
To be fair, I'm very much in favour of reducing the amount that the browser does and to send less stuff to the browser.
I'm in favour of Tom's whitelisting approach and I used to believe this was the best way to consume the web. But that was back when most sites still had an idea of gracefully degrading and continuing to function.
Too much stuff breaks now, and I find that a blanket policy no longer works. Instead I user a combination of Disconnect, hosts files http://someonewhocares.org/hosts/zero/ , private/incognito browsing, to block per-site, to prevent bad stuff getting through, and to prevent sites abusing my use of their site (aggressively tracking and marketing).
But... by and large I now leave core JavaScript enabled. As too much breaks.
Some things will break any way (Omniture code that captures an onclick and breaks the anchor by default unless their JS is enabled). I feel that my setup is a pretty good median point though, between blocking junk and having the web remain usable.