By now you’ve probably heard that PalmOne is renaming itself Palm. Don’t get excited — this doesn’t mean that the PalmSource is being reabsorbed, it’s just a name change.
Note: To clarify, in this article I’m referring to hardware company as PalmOne, the software company as PalmSource, and the two together as Palm. I realized this is a little out-of-date, but without knowing the future name of PalmSource, this seems the only reasonable option…
As a developer of both Mac OS and Palm OS software, I can’t help but compare this to Apple prior to the the second coming of Steve Jobs. Taken as a whole, PalmOne and PalmSource lack direction, and are floundering around trying to write a new OS to replace their increasingly outdated current version, and is full of indecision, infighting and confusion. Further, the new OS won’t be brought to market even if it is even finished. Talk about second system effect. Worse, split across two companies, it is unlikely either company can turn the mess around.
Let’s face it: the licensees are useless. Sony’s gone, Tapwave’s gone, what’s left? Oh, sure, you can pick a half dozen names, but can I go down to the store and buy any of these devices? No, of course not. Do I care that some little company is offering a Palm OS 4.1 based smartphone in parts of Asia? No. I bet you, dear reader, don’t care either.
So on one side of the fence, we have PalmSource: Writing and rewriting an operating system that nobody cares about. Getting a royalty from PalmOne’s device sales, and essentially offering nothing in return. On the other hand, we have PalmOne: Going down increasingly convoluted paths trying to teach a pig to sing, while a replacement animal that can sing and dance is already available.
This latest move is interesting, but I think it completely fails to solve the core problem: One of PalmOne or PalmSource needs to buy the other, and then they need to focus on creating a great mobile platform… operating system and hardware. Linux is not the answer. Linux isn’t even an answer for this problem. The problem is lack of any kind of direction — Linux is not a direction, it’s a kernel. In this context, it’s a buzzword. Applying buzzwords to a problem does not fix it.
PalmOne/PalmSource, you need to find a way to kiss and make up. Every day I am more convinced that you’ll hang together or hang apart. Can’t do it? Oh well. Maybe Microsoft will hire your engineers when you disappear completely and produce something actually useful next round.
Oh yeah: And make your development tools suck less.
Readers: Have no fear. Positive attitude will resume in the next blog entry. In the meantime, here’s some @#$%ing kittens.
Update: On reflection after a comment from Ben Combee, this doesn’t quite say what I want it to. It is the union of PalmOne and PalmSource I expect to see fail, because it appears to be a completely dysfunctional relationship.
I do think there is hope for the platform, but I think the hope comes from PalmOne rather than PalmSource. It’s called a fork. And it’s about accepting that the two branches will never be reunited. PalmOne might actually teach the pig to sing. It’s a tough task, but it just might be possible. It’s rained fish, after all. Can teaching a pig to sing be that much harder?
PalmSource, on the other hand, has wasted a lot of money building its second system that nobody else wants. I think if PalmOne is going to succeed, it’s going to have to be in spite of PalmSource instead of because of them.
And I really hope there’s a buyout clause somewhere in there PalmOne can activate when PalmSource dies…
But you still need a plan for updated tools. Codewarrior Palm 9 isn’t going to cut it forever.