Live data from Hacker News

Why native development sucks and HTML5 rocks: Porting to Windows 8

gkosev.blogspot.com

21–22 of 22 posts

Re: Why native development sucks and HTML5 rocks: Porting to Windows 8

#21

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…

You may be interested in Chrome and NaCl and ChromeOS.

Re: Why native development sucks and HTML5 rocks: Porting to Windows 8

#22
post #10

I've done non-trivial projects in both HTML5 (with/without PhoneGap, with/without jQuery Mobile), Native (ObjC, WinMobile), and hybrid mix of HTML5/Native (views in HTML, model/controller in Native). I've heard all the pros and cons of both sides but most of them are either non-issues or wrong. ARGUMENT: Native is ALWAYS faster than HTML5 MY EXPERIENCE: So what? Speed depends on what you're trying to do and how. Anim…

I have an Android device so can you point me to a single non-trivial HTML5 app in Google Play that is comparable in performance and functionality to a typical well implemented native app?
Post reply on HN