I will check out Enyo, thanks (and megaduck too) for the tip!
http://www.hp.com/hpinfo/newsroom/press/2011/111209xa.html?m...
The WebOS Internals team is happy to accept any patches which are then made available to users with Preware.
So you don't have to wait to get started and we would love more hackers joining the effort. We are also usually available on #wosi-dev on IRC.
- Because WebOS has more real devices out there, and for cheap. - Development for the platform is ~solved~ and nice (including nice emulator images) - I prefer the card view / just type experience to what I know from MeeGo []
: I was a huge Maemo fanboy in the past, got a couple of their shirts and went to their summits. Still own a N810, but it's mostly a clunky music player now. For me Maemo & MeeGo died by now, WebOS is in a state between worlds and might survive (after this announcement) with some support.
I'm not sure whether Web OS can survive without both current devices and active development by HP. I'm fairly certain that Open Source developers alone won't be able to advance the platform to the next level, although I'm sure that there is a lot that they can contribute.
With that said, I'm sure there is a lot of interesting technology that can be mined out of Web OS and integrated into other devices.
WebOS > Android
Maybe RIM could adopt it instead? They could really use a better UI, plus a platform that actually scales well to tablets. Plus they have a large enough install base that once they get rid of their disastrous programming environment developers might actually start writing good apps for their phones.
But yes, it's great that two things came out of Nokia+Microsoft: Microsoft finally has a really solid mobile hardware partner, and Nokia finally has a well-designed operating system.*
*That they care about. Shed a tear for MeeGo Harmattan.
It's still hard to say whether the decision to basically can Meego and bet everything on WP7 was the right one. But at least there was some kind of a case to be made on WP7 having a larger potential ecosystem, and Microsoft being willing to give Nokia huge bags of money. For WebOS it would have been a case of downgrading in every important sense. No real eco-system, no in-house experience, no other company backing it, no real technical advantages over Meego.
The one thing I'm really excited about though is that the developer tools are second to none. Microsoft has made it very simple to build very nice looking applications very quickly. As a developer that just moved to this platform I see the limited apps as great opportunity to help improve this platform even further and I plan on doing just that!
I can see WebOS being concurrence/counterbalance to Android and W7P (mostly Android) for other phonemakers than Samsung (who already has bada)
HTML5 apps are apparently wrapped in AIR internally, and maybe that's what made my app more laggy than in iPad Safari. But HTML5 app dev is nothing new for RIM.
I don't think that's true. Adobe AIR is supported for apps but the actual UI is native.
We're talking about RIM here, how would web technologies (a game they are still late at) "capitalize on their streights"? Let alone "patch over their weaknesses"?
As an aside, I always thought it was weird that QNX was owned by Harman for a while...
Having a application development platform that has actual developers and a growing community would path over the weakness of Adobe AIR, which has neither.
Disclaimer: I am part of the WebKit team at RIM.
Nobody wants to have to open a browser and load a bookmark to get to an application that has browser widgets taking up space at the top, bottom, and side of the screen. They want a home screen icon they can tap once and get an application with native look and feel. If developers can write that app in HTML5/JS then it's a win/win for both developers and users. Developers get a highly portable framework that allows them to rapidly develop software and users get a native app experience.
I guess HP could enforce the patents to keep those innovations locked to webOS but it's kind of hard to do that AND promote webOS as an open solution for people to use.
There's a lot of folks (myself included) that would have been happy to jump in and assist, but couldn't due to the closed-source nature of the platform.
The real prize, however, is Enyo. It's a great Javascript framework, and works in virtually any webkit-based browser. The biggest problem was the licensing terms: You could only use it on WebOS phones. Now that barrier's being removed.
I'm really looking forward to this. Can't wait to dive into the code. :)