"if you could solve all kinds of mobile apps using html 5 , css etc all would go this way"
Check out the demos etc. There's not much you can't do now, and don't forget there's an open API to build those integrations with the device that are not already available.
"I hope that later there will be also new Java SDK on top of QNX"
The billion dollar question is, why isn't there a JVM and SDK prior to the Playbook launch?
For those that didn't already know, QNX already provides JVM support on its Neutrino RTOS. So how come RIM didn't release a JVM and SDK using the existing JVM?
My intuition is that the lack of a published Playbook JVM is in some way related to the legal situation over Java licensing. Googles hijacking of the Java standard with Dalvik may have provided a more efficient JVM, but it has effectively created uncertainly over the very existence of the language.
Personally I'd like to see a quick resolution of the Oracle patent suit, with Google settling with Oracle in the wider interest of the Java community. Not that its likely to happen. In the meantime should RIM use the Java standard they'll always be at a disadvantage to Androids JVM.
It will be interesting to see just what RIM puts in place as a "player". As I say, its hard to see how something that runs compiled Java class files wouldn't be classed as a JVM.
