The problem with HTML5 as an app interface isn't getting something to appear on the screen on any of the browsers, it's getting the user experience to match the native platform. A similar post in 1999 would have been titled: "Why native development sucks and Java Swing rocks: Porting to Mac OS 9"
Exactly! HTML5/CSS/JavaScript are finally moving in the right direction. However, what we should be doing is making the browser nothing more than an x64 VM. That way, all of the underlying OS calls could be wrapped in an OS-independent way, and for those that are specific to a particular platform, a generic way to access host-specific features. Because each generic OS call maps into a real OS call, every call can und…
Re: Why native development sucks and HTML5 rocks: Porting to Windows 8
#21You may be interested in Chrome and NaCl and ChromeOS.