Featured Posts

How to background load and cache UIImageViews images It's often the case that the apps I am working on are required to download quite a couple, or even a few dozen, images and display them in a UIImageView. In looking online I found a few different methods...

Readmore

It sure does snow in Kansas! This week I am visiting my Grandmother in Kansas. Monday night I arrived at the farm just as the first snow was falling, and by Tuesday morning I couldn't have left if I wanted to. Here are some pictures...

Readmore

*Warning* Do not install software included in Panasonic... Background A while back I purchased a Panasonic camera that can not only take pictures, but also record video. I chose the camera because of this combination, in combination with it's optical zoom. Now,...

Readmore

UPS continues tradition of poor service Warning, rant ahead! I don't like posting such, but UPS is making my life miserable often enough that I feel I have to. Anyway, I purchased a product recently which the company shipped via UPS with...

Readmore

Suggestions to correct iTunes / iPhone music sync Recently I had a coworker who upgraded his iPhone to 3.0 find that he could no longer sync that iPhone with his iTunes music library on a Windows computer. It would, however, sync just fine on a Mac OS...

Readmore

  • Prev
  • Next

When is a WebOS “OK”?

Posted on : 21-07-2009 | By : Lane Roathe | In : Development, featured

0

So I’ve been wondering for a while now as product announcements get made and the online and press communities react: when is a WebOS a good thing?

Specifically, for instance, when Apple first announced the iPhone, it provided developers with a WebOS based API set for delivering applications to end users, including the ability to run multiple applications at once. This was immediately trashed by just about everyone.

However, when Palm announced they were ditching their traditional c/c++ based OS and replacing it with a WebOS, the same people who trashed Apple for the same decision were gushing over what a brilliant move Palm was making. And they are equally thrilled about Google’s WebOS announcement.

Perhaps it was because Apple didn’t try and come up with a clever marketing term (ie, WebOS) and instead just called it what it was, a development environment based on a Safari. Both Palm and Google are providing exactly the same thing, a traditional OS at the core with a sophisticated web browser as the “operating system” that the end-user and developers are sand-boxed in.

I’m not saying that a WebOS is not a good idea, I thought that Apple’s offering was pretty nice but admit that I wasn’t interested in developing for it until the Obj-c/c/c++ API was announced. By the exact same token, I’m not really interested in developing for the Palm or Google offerings for the same reason; the type of apps I develop are not that interesting from a developer standpoint on WebOS based API’s.

What I’m really wondering is why sometimes the general opinion is that a WebOS is great and other times the same general opinion is that a WebOS is terrible.

Write a comment

Powered by WP Hashcash