11–20 of 21 posts
Or it could end up dead. No products = no development. No development = dead. WebOS will have exactly the same fate as so many great OS that had zero commercial backing, let alone products. Let alone that it'll fall massively behind the current market leaders and never be able to catch up again..
I bet Samsung, HTC, Sony, etc. all want to reduce their reliance on Android now that Google will soon own Motorola.
It's going to be really interesting to see how it plays out. Even assuming it does get adoption, the most likely path is device makers and carriers taking the open source version and customizing the crap out of it and releasing their own "closed" versions of it, just like Android. And if HP does anything to prevent that then what we inevitably have is something less open than Android.
I do very much like the fact that Google now has another player that will keep them honest about how "open" they are.
Exciting. In some ways webOS seems more modern and advanced than iOS and Android because it's using web / cloud paradigms at it's absolute core. Even though I run iOS, the fact that you can build entire apps in Javascript is cool. Hopefully I can get my hands on a touchpad to try it out
Interestingly enough isn't that how iOS started out? At least to some extend. It would be interesting to know how mobile/web would look today if Apple didn't introduce native apps and instead fully committed to web apps.
Then jailbreakers came along, and demanded to be able to run native code, and boom, Apple agrees and we have the App Store.
It's interesting how opinions can change, and choices strike back.
WebOS UI could easily run atop an Android kernel. Programming in some nice web-based toolkit instead of java-like stuff would be a godsend (PS: I always hated java to the bones).
No, it couldn't. If by "Android kernel" you mean the full richness of the existing APIs, the UI framework, UI conventions etc., then no, you can't just mash up two full-featured OS who both need exclusive access to hardware, have their own UI conventions, APIs, different ways of doing the same things (like showing notifications, switching between applications) etc. If by "Android kernel" you mean "slightly modified L…
WebOS UI could easily run atop an Android kernel. Programming in some nice web-based toolkit instead of java-like stuff would be a godsend (PS: I always hated java to the bones).
Exciting. In some ways webOS seems more modern and advanced than iOS and Android because it's using web / cloud paradigms at it's absolute core. Even though I run iOS, the fact that you can build entire apps in Javascript is cool. Hopefully I can get my hands on a touchpad to try it out
WebOS UI could easily run atop an Android kernel. Programming in some nice web-based toolkit instead of java-like stuff would be a godsend (PS: I always hated java to the bones).
Genuinely curious. Why would you want to program in Javascript on a resource constrained device? Seems like shooting yourself in the foot before you start to me.
Or it could end up dead. No products = no development. No development = dead. WebOS will have exactly the same fate as so many great OS that had zero commercial backing, let alone products. Let alone that it'll fall massively behind the current market leaders and never be able to catch up again..
The lack of hardware is an issue in the short-term but we'll probably see WebOS ports for a lot of popular Android devices to start with. From there the not-Samsung, non-Motorola, Android device makers might want to give it a closer look.
Emphasis on could . What we have now is necessary but not sufficient for that to happen. It's going to be really interesting to see how it plays out. Even assuming it does get adoption, the most likely path is device makers and carriers taking the open source version and customizing the crap out of it and releasing their own "closed" versions of it, just like Android. And if HP does anything to prevent that then what…
1. A license that requires derivative works to be distributed under the same terms