Tizen, webOS, & the Future of Mobile Open Source

jfruhlinger writes "When HP announced it would release webOS as open source, it added a competitor to a narrow niche: there's already Tizen, the descendant of MeeGo, which is, like webOS, an open source Linux-based operating system for smartphones. Can they co-exist, or will one come out on top? One built-in advantage for webOS is that already has hardware, in the form of all those $99 TouchPad's being snapped up on eBay."

Comments

Lots of potential here

[na1led]

I think there is a lot of potential for developers to make money and make WebOS into something much better. You already have over a million people with Touchpads plus all those Webos Phones. There work in progress to run Android Apps inside WebOS, and if some can port Netflix and Hulu over then I'm sure it will be a winner.

WebOS is ahead

[Tester]

1. I'm not convinced at all that HP is giving up on WebOS, if they had wanted to get rid of it, they could have sold it for a lot of money. There are many interested buyers.

2. WebOS has a huge advantage, it already exists. Tizen doesn't. Intel had announced that they would announce the architecture at Linuxcon Europe, but they had nothing to show. Rumour is that they're still in negotiation with Samsung.. And doing this kind of work in a joint venture is always a terrible idea as there is no clear direction. On the other hand, WebOS exists, works and is on devices already. And it seems HP is still investing in it. Also WebOS has applications, Tizen doesn't, it doesn't even have any defined APIs, no one knows what will be in it, etc.

Re:Abandonware open source

[Junta]

It's really small details that make a big difference to me. A coherent, unified messaging app (simple trick of using libpurple, mostly). The ability to sanely manage multiple text conversations at once ('cards' compromising between full fledged desktop metaphor and mobile form factor). Architecture that prioritized keeping running apps running instead of arbitrary kills on 'background' applications. Architecture that didn't encourage every task switch to induce piss-poor home-written state restores (why is it when I switch to a browser, my SMS conversation closes when I switch back???).