I'd say that by 2014 everybody will have forgotten about HTML5 anyway
Truth!

How ignorant are you two? Absolutely everyone that means anything in the computing industry is pushing HTML5 like there's no tomorrow. Examples:
• Apple, by not including Flash in iOS and no longer including Flash by default on Macs.
• Microsoft, by declaring that Windows 8 will support 'native' HTML5 apps.
• Palm/HP, with Palm webOS, and the Mojo and Enyo APIs.
• RIM (Blackberry), with Blackberry OS supporting native coded HTML5 apps.
• Google, again, native HTML5 apps.
• The browser makers. Apple, Mozilla, Google, Opera, Microsoft are scrambling to optimize their Javascript engines so as to have the best HTML5 performance.
• Facebook: HTML5 apps (will soon?) be available as 'FB apps', companies like Zynga interested.
3rd party utilities like PhoneGap and Titanium, both open source, serve as HTML5 'compilers' that package apps for various mobile and desktop platforms.
HTML5 is the future, if you don't accept that as fact, then enjoy being left behind while smarter developers embrace these kinds of technologies.
Finally, I am a member of the GMHTML5 Beta programme, and I must say that the performance of several games (Karoshi, They Need to be Fed, to name a few) is pretty fantastic, even on mobile devices like my iPhone 4, and an iPad 2 I messed around with. iOS 5 and its new JavaScript engine is optimizing that even further, and TNTBF runs perfectly on 'slower' devices like the iPad 1.
Hey man, no need to get angry. HTML5 is a cool technology, I'm just skeptical about how everyone touts it as the greatest thing since integrated circuits. I also think that you should separate between HTML5 in the browser, and these "native apps via web technology" frameworks. The native frameworks are just a smart way to take advantage of developer mindshare of JS and CSS. Unity was similarly intelligent in making UnityScript a javascript variant.
I'm especially skeptical about HTML5 replacing Flash in the browser in the near future. On my machine at least, <canvas> is eating just as many CPU cycles as Flash would. It's a pain that you have to manage focus with the Flash plugin, but has that ever been more than a minor inconvenience? Companies like NBC, HBO, Youtube, blip.tv, and other video services are also going to have to invest *a lot* in figuring out how to seamlessly control video access and do ad overlays.
Palm webOS is dead, HP is officially transitioning out of the consumer market--that goes for TouchPads, desktops, and laptops (possibly with the exception of consumer-grade printers). WebOS will likely live on in the form of some kind of enterprise development platform, but do you really care about that? Also, Blackberry jumping to support HTML5 apps is clearly RIM trying to jump on the bandwagon. They know their standard app SDK is awful to use, so they're grabbing onto something they know everyone will be familiar with (and frothing at the mouth about).
I'm not as familiar with Google's plans with native HTMl5, so I'll take your word for it. But on Windows 8, you can clearly see from the demo videos that HTML5 is a second class citizen. The WP7 development environment is a very controlled one, so you can expect there to be similar limitations from making these 'native' HTML5 apps full-featured. For christ's sake you couldn't even open a socket on WP7 until the Mango beta came out.
And regarding OS X, PCs often don't include Flash by default, and playing games in the browser on iOS, even if the developers go out of their way to optimize performance, is crap. The performant HTML5 games I've played on iOS require you to "Add to Homepage" anyway, so at this point, I'd rather just download your game from the App Store. The only downside being that as a developer you have to pay the $100 developer fee. Oh well.
I don't actually think that people will forget about HTML5 by 2014. Just that its role will be more clearly defined by then and it definitely won't be the one-technology-fits-all furor that people are going crazy about today. I'm seeing it as being closer to the status quo we have now: HTML5, whether converted to native or not, will have the benefits of rapid development with the disadvantages of not being specialized per device. Yes, we'll be able to detect platforms in the js, but you can't possibly expose *every* major native API to Javascript.
Javascript is a great language. But when working on significant games and applications I like languages with a little more structure. So aside from pet projects, the majority of my work will still be in slightly more static languages (AS3, C#, C/C++).
Anyone who's anyone in the industry knows HTML5 is a very important part of the future, and with the performance HTML5 has now, I daresay it can easily compete with flash right now.
One word: audio. Doesn't matter for "apps", but games are boring hell without the pew-pews and meedly-meedlies.
Just remember, the world runs on C and COBOL.
------------------------------------------------------------------------------------------
Slightly more on topic:
I'm curious, how does Construct fare with people who come from a GM background? I'd rather not spend any money on a prototyping tool, much less $40 for one with an inferior Mac port.