We all know Mike Cane, and most of us share a strange dislike for him(not me though). Well, the poor guy wrote an editorial with PalmInfoCenter-and he immediately got a nice flogging. Serves him right, doesnt it?
Actually, it does not serve him right. Altough he chose an extremely provoking title-nobody does like beeing called a sucker- and made a few big mistakes comparing kernel and API, two of his core statements are sensible.
Lets start with him stating that OSses shall soon be interchangeable. While this definitely wasn’t true a few years ago, the Palm OS nowadays runs on ARM processors. Same architecture like PocketPC, Symbian, Linux and a load of other OSses. Lets face it-my stock Siemens SX1 almost equals a Tungsten T without touchscreen(OMAP CPU, 4MB of RAM, pretty big screen(higher resolution than Zire 31),bluetooth, MMC-Slot,…) . And a standard PPC is more-less a Palm OS handheld with more ROM and a different screen format!
A german reviewer(I know him as a trustable source) even found out that the T3 was produced with ASUS-a company that is known for a huge selection of PocketPCs. I think that the dominant question in the following years will be: Touchscreen?
Next thing:
Mike thinks that PalmSource will soon start porting the core Palm OS PIM apps to other platforms. Many commentators thought that a suite of Date Book, To Do, Address Book and Memo Pad would have no chance on the market. However-lets face it. What is Outlook? It is essentially the same thing bundled with a decent email client. If you think that Microsoft should stop developing Outlook, come on and mail’em! See what they answer you, it will be funny for sure!
What do you think about my statements?
P.s. Thanks to Steven Fisher for pointing out the thing with the API!
Related posts:







[...] Most of you probably already read Sagio’s report-the Windows Mobile Treo will be accompanied by a PalmOS cousin. Immediately, the PIC went bonkers…. and forgot Mike Cane’s editorial about operating systems(act of shameless self promotion: and my answer). [...]