No app store? No problem: Grooveshark rolls out full HTML5 site for all devices
From the article: "I experienced minimal complications when using Safari on both the iPhone and iPad"minimal complications is a euphemism for "Any normal user would throw the thing against the wall in frustration."To me this is just further demonstration of the failure of HTML5 on mobile. It's been, what, 4 years we've been in the "HTML5 will save us all" hype bubble?Don't get me wrong; I am building a webapp and aspects of HTML5 have made my life far easier than if I were still in 2008. If I had hair I'd still be pulling it out due to the complexities of CSS (even with things like LESS) and subtle browser differences would turn the rest of it gray. But the current state of HTML+CSS+JS on the desktop is pretty good; compared.We appear to be years away from a similar state in mobile. Between Safari's problems with no JIT support within apps and the fragmentation of Android, coupled with the monstrosity known as IE on WP7 (and WP8 and Win8), it is just not possible to use "HTML5" to build a great mobile experience (and reach a large audience).My history in working with the W3C (I worked on HTML 3.2 and  4), and my understanding of the asymetric competitive nature of the major players (Apple, Google, Microsoft) makes me believe this situation is not going to radically improve anytime soon.The upside is dev tool vendors who can help ease the pain should do pretty well (e.g. things like Xamarin (C#) and MoSync (C/C++/JavaScript))...