And all this on top of the fact that HTML was not intended to build apps and it shows. No matter what is built on top foundation will still be messy and shaky.
Just a few months ago I was working on moderately complex web app and even with some nice tools helping to bring some sanity into it (backbone, coffeescript, etc.) we had to reinvent a lot of thing that native APIs give you for free.
It really makes me wonder about those proclaiming superiority of HTML5 over native:
did they build anything nontrivial in it and did they try to do the same with native
approach.
Alas, I see html approach as "mediocre everywhere and pain to develop". And I say this as a guy who does know HTML, CSS and JS :(
As a contractor most of the projects I work on are web based ones.
Every time I manage to land a native application contract I am thrilled to get away from such headaches.
Specially the ones discussing pixel level behavior with the customer or trying to making him/her understand why certain desktop like features are not possible at all in a browser world.
It really makes me wonder about those proclaiming superiority of HTML5 over native: did they build anything nontrivial in it and did they try to do the same with native approach.
Alas, I see html approach as "mediocre everywhere and pain to develop". And I say this as a guy who does know HTML, CSS and JS :(