.Neo, on 12 September 2012 - 00:00, said:
It's fine to rely on HTML5, just not to the degree where you completely replace native apps by the technology.
It's not fine to rely on HTML5 because:
A) It barely works on maybe 50% of the browsers
B) It doesn't even work properly on mobile through a browser (fragmentation is even worse with feature sets) and on mobile it's even worse.
C) It's slow and any interactivity is a DOG on CPU and on mobile again tons of features don't even work right. Differences between iOS and Android implementation to start.
D) It doesn't have access to native APIs but only those who are supported by the browser and even then the supported APIs differ from one browser/platform to another.
E) It's not even finalized and now W3C and WHATWG have split the spec in two versions making even more problems with compatibility
F) It's just SLOW as hell. It can't even compare to anything native and even Flash. It's just slightly modernized HTML platform (not finished with specs I might add because they can't agree on many things) that is still relying on 15 year old scripting language that hasn't evolved at all and the foundation of the issues with HTML haven't been solved. They just tried to build upon an already broken model that is dependent on browser support for features.
G) Google, Mozilla and Microsoft are all trying to create their own HTML5+ specs that they think benefits their platforms. It's basically a clusterf***
The only thing HTML5, and actually HTML by default has, which is nothing new, is usability over the content shown as it is easily searchable due to it's semantic nature but even that is not really HTML5 thing.. This was a fact even before HTML5.