Linked by snydeq on Tue 16th Aug 2011 16:46 UTC
Web 2.0 InfoWorld's Peter Wayner discusses the 11 hard truths Web developers must accept in making the most of HTML5 -- especially those who are looking to leverage HTML5 in hopes of unseating native apps. 'The truth is, despite its powerful capabilities, HTML5 isn't the solution for every problem. Its additional features are compelling and will help make Web apps formidable competitors for native apps, but security issues, limitations of local data storage, synchonization challenges, and politics should have us all scaling back our expectations for the spec.'
Permalink for comment 485542
To read all comments associated with this story, please click here.
Speed required
by ephracis on Wed 17th Aug 2011 15:52 UTC
Member since:

While most people see future web apps as more basic application aimed at consumers I have recently been in charged of creating specialized tools for internal use at a company. Of course, these tools had to be HTML5.

You will get into trouble when you are working with lists of several thousand items (some of our databases have row counts in the millions) and while just doing iterations in pure JS is pretty fast the slowest operations are DOM manipulation and changing the "GUI".

You have to know a few tricks and make good use of localStorage and WebWorkers (+ a lot of ajax to reduce those hundred of thousands of rows to "just" a few thousand) if you want to get these kind of things done. Something you don't have to deal with in native apps.

Mind you, that these issues are not only related to niche, complex applications. Just take the example of a music application. A lot of people have a library of several thousand tracks and working with that in a native app is no problem, but creating an <li> and doing JS manipulation on it will get you closer to the limits of JS speed.

So while some people say that the JS speed race is merely artificial at this point I say: give me moar!

Reply Score: 2