On a mobile unit, sure. But JavaScript powers keyboard shortcuts, my favorite Gmail feature. If that costs me CPU cycles or bandwidth latency, I don't notice it. I appreciate simplicity but on a modern computer/browser, efficiency and features often trump convention and portability.
All this discussion makes me think that if someone were to create, say, a Firefox plug-in for accessibility -- one that could react to Javascript-related DOM changes and such -- there would be a serious market for it.<p>Of course, if web developers would stop being lazy and properly implement things like progressive enhancement and graceful degradation, it wouldn't be needed. Every site I make starts as non-Javascript, even if I plan for the entire thing to be laden with it in the end.<p>Then again, all of this is moot anyway, because the author gave absolutely no reasons for why he prefers the HTML version and doesn't use the JS version. I am going to run with the idea that he fears <i>JAVASCRIPT GNOMES!!!</i>
I would NEVER cater for an audience that willingly switched off javascript. This is like people who refuse to buy any cars that have electronics in them. Javascript is no longer some esoteric or slow - it's supported by 90% of all browsers, and pretty much critical for most of the web.