Open webOS 1.0, Enyo 2.0, and fulfilling the revised dream | webOS Nation

Open webOS 1.0, Enyo 2.0, and fulfilling the revised dream

by Derek Kessler Wed, 25 Jan 2012 7:55 pm EST

In 2009 the dream of webOS and the Palm Pre was a successful web-based mobile platform with full-featured apps built with web code. It was an ambitious dream, but it came packaged with a flawed plan and debilitating lack of resources. The idea of building apps with just HTML5, CSS, JavaScript, and a sprinkling of custom code seemed so obvious and yet something that nobody had yet grasped.

There's a reason nobody had yet grasped it - it's not easy. Sure, programming in HTML isn't exactly rocket surgery, but building an OS to support solely those apps is a more difficult proposition. It took webOS a while to get its footing, too long, in fact.

Today the dream has been revised. webOS is still at its core based on web technologies, but the dream is of those web-coded apps being everywhere and breeding success back down to the to-be-open-sourced webOS. Today's open sourcing of the Enyo application framework was the first of many steps to fulfilling that dream, and it's a pretty big one. It didn't take long after the announcement for Enyo-based apps to find their way into our browsers and other platforms, and we imagine that's just going to be the beginning. There are plenty of well-built Enyo apps that we're certain developers will be excited to be able to bring to other platforms without much effort (at least compared to the effort of completely rewriting the app for other platforms).

Today was really all about Enyo. Having the roadmap for the webOS open source release is great and all, but it's just to set expectations. We now know what we can look forward to in the coming months (ha, gotcha!), but at least in our estimation the most interesting item on the list was the very last one in September 2012: Open webOS 1.0.

This is not HP going back and pulling webOS 1.0 out of the vaults and open sourcing it. Nor is this HP dialing down the version number on 3.0 and shoving it out to the public. As we discussed last month after HP's announcement of their open source plans, there's plenty of work to be done with regards to open sourcing webOS. And today we got a glimpse at some of that work, such as adopting the standard Linux kernel for distribution onto more devices with better driver support and switching to JavaScriptCore over V8. These changes weren't just made with "going open" as a concern, in fact we wouldn't say that was a concern at all, though certainly a nice bonus as a result. The idea behind these changes (and likely plenty more to come) was to make webOS hardware agnostic - more like Linux and Android.

The revised dream is that by making webOS a new alternative to Android they might be able to pick up some marketshare in the process, making it easier to justify bringing back webOS hardware from HP. That's part of why HP's reseting the version counter to 1.0, and maybe pulling off a rename here to Open webOS (though personally we're still likely to just call it webOS if that's the case).

That's the dream. Now if that will be the reality, that remains to be seen. But at least today's news not only puts us a step closer, but also makes it an actual possibility. An open source application framework is one step, but we have to hope that Open webOS 1.0 takes massive leaps ahead, because that's exactly what the competition is going to be doing too - and they have hardware to back it up.