Plenty of products are successfully using HTML5 for applications where it makes sense and are succeeding with it. Blanket generalizations are usually wrong.
I think you simply refuse to understand - a nail may be pinned using a pickaxe, but when you have a hammer available, which does the job neat , why would you go for the pickaxe? HTML5 is the pick axe which does the job ugly. Mobile developers have little reason to adopt it.
Comments
Part of HTML5's origin is a draft standard called Web Applications 1.0. HTML5 is meant to be a desktop and mobile app replacement technology.
http://en.wikipedia.org/wiki/HTML5#Standardization_process
Intent do not always translate to reality. HTML5 does not deliver for mobile/desktop. End of story.
Plenty of products are successfully using HTML5 for applications where it makes sense and are succeeding with it. Blanket generalizations are usually wrong.
I think you simply refuse to understand - a nail may be pinned using a pickaxe, but when you have a hammer available, which does the job neat , why would you go for the pickaxe? HTML5 is the pick axe which does the job ugly. Mobile developers have little reason to adopt it.