Slashdot Mirror

← Back to Stories (view on slashdot.org)

Palm OS Spinoff

Posted by Hemos on from the interesting-move dept.

iCharles writes "According to this SEC filing per this Palm Infocenter story, it would appear that Palm is spinning off its OS devision. I'm a Handspring user, so it sounds quite interesting to me."

3 of 107 comments (clear)

  1. No Linux in Sight by GrouchoMarx · · Score: 5, Insightful
    Several posters so far have speculated on what this all means for Linux on the Palm. In truth, it means absolutely nothing.

    When Palm eventually moves to ARM-based hardware, I'm sure we'll see creative, inventive people making Linux ROM images for the hardware the same as they have for the iPAQ. But they won't be coming from Palm Solutions (the hardware/parent company), and I sincerely doubt they will be coming from any of the licensees. Why jump ship from a platform that had 80% of the retail market in August of this year, in addition to 80%-90% of the market for the past six years? That's foolish.

    In addition, there is a world of difference between a Linux PDA and a Palm PDA. The PalmOS is built from the ground up as a handheld, all-in-RAM, XIP OS. Linux is originally a server OS. Yes, there has been absolutely astounding work in recent years in bringing Linux into embedded systems, but that's not enough. The paradigm of Linux is the same as the paradigm of the PocketPCs; a file system. The PalmOS has no file system, save for on expansion cards which are a new development. It's a database-like in-RAM format. That's what makes it so fast. You can get better performance out of a 33MHz Palm than you do out of a 150MHz PocketPC. There's a fundamental archetectural reason for that. Sure, Linux and Win32 may be familiar for many developers, but in order to do it right you need an archetecture and API that is designed for that type of system.

    There's also the UI issue. The Palm UI was designed with Mac-like simplicity and consistency from the get-go. (Not surprising, considering that the majority of the founders were ex-Apple ane ex-Newton people.) The "Zen of Palm", alternately the subject of praise and flame wars, is really what made this organizer work as a portable computer. For cultural reasons, Linux doesn't have that. We (Slashdot readers) put up with a great deal more disparity in UI across a Linux desktop than a handheld user is willing to deal with. Simply throwing KDE or QT at it won't solve the problem of a UI that is consistent, learnable, and has almost zero learning curve.

    Sure, a company could take the Linux kernel and tools and write a Palm-esque interface for it, and rewrite the guts enough to be naturally resource-based XIP. But by that point, you're almost writing a new OS to start with. And every company is going to have their own "redux Tux", which means you won't be able to generate a single executable file that you can throw on any device, the way you can with a Palm. One truism of the Open Source / Free Software (whichever camp you are in) movement is a lack of unity in APIs and UI. That will kill any mass market attempt at a handheld. The market is not interested in a device you can tweak and customize and recompile. It wants a device you can charge, pickup, and use. And at least right now, Linux is not that.

    --

    --GrouchoMarx
    Card-carrying member of the EFF, FSF, and ACLU. Are you?

  2. Re:Spinning off an OS division. What about BeOS? by GrouchoMarx · · Score: 5, Insightful
    Palm's reasoning behind buying Be was very sound. They didn't want the BeOS codebase. It doesn't fit into a handheld. Neither does BeIA, which is designed for the niche-that-wasn't "Internet Appliance". They wanted the people who wrote a multithreaded, multitasking, multimedia OS in the first place.

    Palm: Hey, you guys wrote a super cool OS for the desktop that rocked, and you did it relatively quickly, too.
    Be engineers: Thanks!
    Palm: We've got to write a new OS for the ARM archetecture that is fast, multimedia-ready, and backward compatible. Think you can do it?
    Be engineers: Uhhh...
    Palm: Here's $11 million, we just bought what's left of your company.
    Be engineers: Sure!

    Don't look for BeOS to appear on the Palm anytime soon. Look for the same kind of cool developments on the Palm, this time with a market share that can actually appreciate all that hard work.

    --

    --GrouchoMarx
    Card-carrying member of the EFF, FSF, and ACLU. Are you?

  3. Re:KDE/Qt Embedded won't fly on Linux handhelds by mj6798 · · Score: 5, Informative
    1) When was the last time your manager needed X11 remote display capabilities?

    Remote display is extremely useful for developing software for the handheld and for debugging it. Also, a 200MHz handheld is a powerful machine--with X11, you can use it like a desktop and with desktop applications running on it when you connect it to a network.

    2) Why the need for different toolkits?

    Because there are already lots of handheld applications written for toolkits other than Qt. Face it, the world isn't going to switch its vertical application development to Qt just because some people think it would be nice.

    On a PDA, a single, integrated, interface is the way to go.

    If you think "consumer market", perhaps. But Linux PDAs are for vertical apps, and the cost and success of vertical apps is driven by ease of development and porting among platforms, not by some nebulous notions of appearance. Multiple toolkits are a reality in that market.

    Linux programmers need to start programming apps for 320x240 displays, and QT/Embedded sounds like a good place to start.

    FLTK and Java are already much more widely used than Qt/Embedded, and they don't cost anything.