Developers: webOS Lives Up to the Hype 12
We’re admittedly a little late to the game on this one, but we’re none-the-less happy to report that early developer feedback is pointing toward webOS living up to the hype. John Cox from Network World has written up an excellent article covering some of the early work done with webOS, as well as a great explanation of what makes up the webOS operating system.
Cox does a great job of hitting the key points such as multi-tasking, web integration (Synergy), and the use of pre-existing programming languages. He also offers up one of the better explanations of how Pre applications will run, that I’ve seen. I highly recommend jumping over and giving the article a read, if you haven’t already.
Do we have any developers out there that have had a chance to work with webOS? Is the article spot on, or are they too biased in one direction or another? Give us your thoughts in the comments (even if you aren’t a developer)!
Thanks to everybody that sent this in!
12 Comments
I get that many developers have the same issue, but there are plenty that give away their programs for free, regardless of whether it is open source or not. Why are some folks surprised that developers would give away their source code? They have been doing it forever. Look at the apps on freeware-palm.com for example. They are not all open source, but many are.
From a business perspective, the company that has the most to gain by giving away free Pre apps is Sprint. The more webby, the better. Bandwidth hogging apps will make for some fat usage bills for Sprint. If they were smart, they would host and sponsor apps, for just that reason. I doubt that they think this way, or more precisely, the people that are in charge don't think this way because they only want to add software and services that can be used on all phones. The advantage that the Pre has is that many of the apps could be cloudy, and thus easily ported to other phones.
thanks for the information on the ability to integrate with synergy, that's been my biggest question for the twitter app i've been working on. since an open source project didn't rate high on their list for sdk prerelease, i've just been working on getting the behind the screen stuff working on browsers. the twitter API sure does make javascript development a breeze.
Thats great news! Thanks!