> How quickly these bugs (and perfomance issues) get fixed
> will have a huge effect on HTML5 vs. native adoption.
Hardly. I say that as a guy who've spent more than a dozen years making web. HTML does not scare me, I like CSS and can do fancy stuff with it, I have no problem with JavaScript.
I am moving however to Objective-C and Cocoa world. It is so clean and tidy compared to the mess the web technologies stack is. And no matter how great support for HTML5 will be, no matter how performant it becomes—it will be well adopted and very performant mess. We can bring in frameworks and libraries, duct-tape things together, but we are long past the point where we could get rid of all the ugly heritage.
My feeling is, that web technologies will be used mostly for the content leaning apps, and for "apply" the native will be a clear choice.
Then there is this "cross-platform development" thing. Well, not sure about this one. I guess we are bound either to have mediocre solution for all, or bite the bullet and do native for each platform if best results are desirable.
I am moving however to Objective-C and Cocoa world. It is so clean and tidy compared to the mess the web technologies stack is. And no matter how great support for HTML5 will be, no matter how performant it becomes—it will be well adopted and very performant mess. We can bring in frameworks and libraries, duct-tape things together, but we are long past the point where we could get rid of all the ugly heritage.
My feeling is, that web technologies will be used mostly for the content leaning apps, and for "apply" the native will be a clear choice.
Then there is this "cross-platform development" thing. Well, not sure about this one. I guess we are bound either to have mediocre solution for all, or bite the bullet and do native for each platform if best results are desirable.