Slashdot Mirror
Microsoft, Google, Twitter Debate HTML5
jbrodkin writes "The annual USENIX conference featured an all-star lineup of engineers from Microsoft, Google, Twitter and Flipboard debating whether HTML5 is the 'holy grail' for building next-generation Web applications, and whether mobile developers should build websites or apps. The promise of HTML5 is 'write once, run everywhere,' but the panelists did not agree on whether the technology is good enough to make browser applications feel 'native.' There was general agreement that HTML5 is lacking on mobile devices, and that for better or worse the move toward apps instead of websites is being driven less by technology than the imperative to make money."
Are we positive we want to delegate all to the browser?
- web apps are easy to deploy.
- web apps can't match efficiency of native apps (it doesn't matter when you have a multicore desktop, it matters when your smartphone has way less autonomy than it could.
- web apps everywhere means they will have to be secured (compared with web 1.0 with standard ports for every protocol and a multitude of client/server software vs. port 80 and a handful of browsers)
- web apps can be seamlessly upgraded (even when user doesn't want to, though)
- native apps are hard to deploy (a free OS with package management, look at debian or experiments like nixos, solves this problem)
- FOSS native apps can be owned by the user.
Anyway, this is just a trend. Games will still be native, and people will hold onto their office suites, and some html5 features reduce the dependency from the network (local storage) which is good.
---- MISSING MISCELLANEOUS DATA SEGMENT --- [sigdash] trolololol
and I still think that write once, debug everywhere is better that write n times, and debug everywhere