Palm Pulls the Plug On Palm OS
BobB-nw writes to tell us that Palm has decided to kill their PalmOS operating system and is instead betting their future on a still mostly unknown Palm webOS. Very little is known about the new Palm webOS, but it will supposedly support HTML5 and enable a local data store so that applications can be used both online and off. All of this is rolled into a Linux framework with a message bus based on JSON. Will be interesting to see where they take it.
Worst. API. Ever. EVAR!
Bad enough that they renamed standard library functions. They also changed the order of arguments to those functions.
Windows PocketPC, meanwhile, was programmable using the same languages and toolchain as regular Windows.
Best Slashdot Co
Is this going to be a brand-new start? Didn't they buy Be a few years ago to build their new OS versions around BeOS?
I may be wrong but I thought you only use JSON when you're passing messages between trusted sources.
Is that perception incorrect?
Is it just me, or has Palm fallen flat on its face every time they have something that could be big (except when they debuted the palm pilot)?
They used to have so much caché, but every time I hear what sounds like good news it just vanishes.
Why do people keep supporting this company if they can't get their act together? Do they offer a magical pony with every purchase that no one is telling me about?
-
They had their chance when they bought all of the rights to BeOS. They could have taken the kernel and a few components and built a new OS on top of that, back before Blackberry and Apple were huge players in this market. Now, this comes along as a me-too product that will probably have very poor performance (a web-based approach on hardware too slow to run something like a V8 or Gecko-style JS engine?!)
Worst of all for Palm, they could have released most of the code to BeOS under the GPL, let others develop it, and that would have had the effect of crushing a lot of their competition from Microsoft.
I started with WinCE (on a Casiopia) and stayed through 2 revisions despite the crashes, slowness, and rapid battery drain. I switched to a Palm III (clone actually - TRG Pro) and have had 3 Palm devices since then (currently a Centro). I prefer Palm's calendar and contact database to the alternatives. My Palm currently has about nine thousand contacts in the database. Am I going to be able to use the WebOS when there's no wireless data connectivity? I don't think so. Can Palm ensure the security of my data while using WebOS? I don't think so. What happened to the rumored port of PalmOS to Linux? I've been waiting for that for 3 years now. Since they are abandoning the platform, is it for sale? Are they going to open source it? I would not like to see it die.
I was one of those people saying it wouldn't be enough. And I still do think it's not enough for some things.
:)
Making a 3D game and using hardware openGL acceleration is tough to do in with HTML5
I just meant that it's a nice option to have to build some applications. It also allows to make things somewhat cross platform with PhoneGap ( http://phonegap.com/ ) because things like GPS and motion sensors are already abstracted and the implementation to another webkit device wouldn't be difficult.
"If they have both, tell them we use Linux. And if they have that, tell them the computers are down." -Dave Chapelle
I am using a Zodiac 2 now, and have a TX in storage if the Zod dies, but I am wondering what options exist for moving/using my data on other platforms?
I know Access has sold their ALP platform to a couple companies, it's on at least one digital camera, too. They also put out a PalmOS compatible layer for the Nokia internet tablets.
I think there is a company that emulates the basic built-in apps on WinCE and iPhone/iPod Touch. Haven't heard great things about that.
Are there other options out there?
All opinions expressed herein are my own, and not those of my employers, who are appalled.
I still don't have a replacement for the PalmOS application together with the antenna to measure the DECT field strength in the environment. I'm using it all the time to plan a DECT roll out and to define the mount points for the DECT base stations.
Making a 3D game and using hardware openGL acceleration is tough to do in with HTML5 :)
Today, probably. Tomorrow, not so much. From HTML5 draft, section on the CANVAS element:
"A future version of this specification will probably define a 3d context (probably based on the OpenGL ES API)."
So it looks like DN4E will be written in JavaScript.