> So in conclusion, I really do hope that HTML5 isn’t to be the future of the web, for we will have missed a chance to really make the future web great if it tu

> So in conclusion, I really do hope that HTML5 isn’t to be the future of the web, for we will have missed a chance to really make the future web great if it turns out to be so. This final sentence perfectly demonstrates the unfounded, poorly-written, wordy wishful thinking of the entire article. Don’t waste your time. - - - He also demonstrates an utter failure to grasp the HTML5 timeline, or why the DOM matters, or that his "alternative" is nothing more or less than requiring all browsers to support a theoretical open-source release of Java applets / Silverlight / Flash / similar. From one of the author's comments: "I do not see the canvas tag and flash as doing essentially the same thing. Rendering text in a canvas tag would be an odd thing to do for example." Ah! Precisely: one would have to add a shiv to allow <canvas> text to be selected and copied, and it wouldn't quite work the same as it would on the rest of the page; text would be anti-aliased differently than system text; etc. Remind you of anything — Flash, perhaps? He's arguing against himself here.