Palm OS Spinoff 107
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."
It's a naive, domestic operating system without any breeding, but I think you'll be amused by its presumption.
What a great idea! (Score:4, Funny)
Re:What a great idea! (Score:2, Interesting)
Or better yet, if we could only convince Apple to do the same thing! This would free Apple's OS division to aggressively market their products to all OEMs. Imagine if all the owners of x86 boxes out there had the option to install OSX instead of Windows.
I know this has been debated before, but I still think it makes sense.
Re:What a great idea! (Score:1)
Or better yet, if we could only convince Apple to do the same thing! This would free Apple's OS division to aggressively market their products to all OEMs. Imagine if all the owners of x86 boxes out there had the option to install OSX instead of Windows.
I know this has been debated before, but I still think it makes sense.
And been done before, from a hardware standpoint anyway. Then Steve Jobs came back and ended the whole thing. Really, if Apple had any intention of doing this, they would have done it a long time ago.
Be that as it may, Apple's hardware and software are rather tightly integrated, IMHO. Separating the two would be rather difficult; not impossible, but Mac users would not get the feeling of the system as whole. I have used Linux, *BSD and Windows on my PCs, but have not felt like the thing's a complete system like I have when I used a Mac. Am I talking myself into getting a Mac? Been tempted, but no.
So, while I think Apple spinning off the OS would be a good thing for PC users, it would not be so good for Mac users.
Re:What a great idea! (Score:1)
OSX is another animal, the kernel runs on a wide range of hardware,infact you can run OSX on x86 hardware today. Of course on x86 it must be run without the nifty MacOS GUI.. but you CAN run Xwindows on it. It would be possible to port the MacOS-X gui to another platform, it just hasn't been done (yet?)
I like my Mac, but it doesn't run that pile of garbage called MacOS. Linux runs good on it, although I may decide to move to Darwin or another *n?x.
The lagging might stop... (Score:4, Insightful)
Re:The lagging might stop... (Score:3, Insightful)
JOhn
Re:The lagging might stop... (Score:1)
Re:The lagging might stop... (Score:2)
Now just how big are the changes? Of course, there will be driver level changes for different displays, etc.. but the API? Can you give me any sort of proof there is "alot of under hood changes" going on or are you just passing on "knowl3dge" you learned on IRC. In a more radical view of "alot of changes" do you really think Handspring rewrote the PalmOS from the ground up to change "whats under the hood" and kept the same API? Come on...
I'm more than happy to hear comments from people in the know on API changes. Or perhaps even just a reference to substantiate a claim. But just passing on info cuz you think its right and then adding stupid endings like "its called compatiblity" to make yourself seem smarter doesn't add much to the circle of knowledge. If you work for Handspring, Sony, Handera, or even just know cuz you program on Palm Pilots please enlighten us. On the other hand if you are a troll and add a sentence in which you enlighten the slashdot community about "compatibility" then please refrain.
JOhn
Re:The lagging might stop... (Score:1)
about time (Score:2)
and we stood and watched as WinCE got stronger and the Journada and the iPaq get better and better.
i hope this lights some creative fire in both divisions. I wonder if Palm hardware will be modified to run Linux or WinCE?
Re:about time (Score:1)
Information Week [informationweek.com] had an article about it.
hercules using arm? (Score:4, Interesting)
It also brings up interesting prospects for the future of Palm OS. If Palm's OS division is making a Palm OS for an ARM processor, will we start to see Palm OS as an option on iPaq's and th like? It's just my personal opinion, but I like Palm's interface more than WinCE, but right now, the hardware that runs it is slower. I guess we'll see.
Re:hercules using arm? (Score:4, Funny)
Oh come on. "Palm" OS running on an "ARM" processor, but without the "Thumb" extensions to the chipset, being sold by "Hand"spring and "Hand"Era? The possibilities are endless... :-)
Re: hercules using arm? (Score:1)
So you mean a name like Dragonball MX1 [motorola.com] isn't cool enough? ;-)
Re:hercules using arm? (Score:1)
Re:hercules using arm? (Score:3, Insightful)
Also, since the OS division will be it's own company, they can also sell versions of Palm OS for the different hardware available. Like even if Compaq continues exclusively using wince, PalmOS can just compile the OS for the StrongARM processor, etc. And I don't know about the other companies, but compaq would not have a problem with that...they've been very supportive with using linux on the iPAQ. And that makes it seem more likely Compaq will start selling iPaqs with palm.
And now for something completely different (Score:1)
"Handspring" is going to eventually benefit from an OS that has been "sprung" by "Palm"...Oh the pain of bad irony.
Spinning off an OS division. What about BeOS? (Score:2, Interesting)
Re:Spinning off an OS division. What about BeOS? (Score:1)
Re:Spinning off an OS division. What about BeOS? (Score:5, Insightful)
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.
Clever move, but late (Score:2, Interesting)
Changing direction for Palm is clever, but one has to ask if they aren't late: Developing a new OS might take 2 years, while WinCE is pretty much there.
Disclaimer: Yes, I have a Palm. No, I dislike MS.
Re:Clever move, but late (Score:3, Informative)
Nobody beyond a handful of wannabe-geeks who want to say "look what my handheld can do!" give a damn about multimedia on a handheld. "Ooh, I can look at 3"x2" color Powerpoint slides, and listen to supercompressed MP3s over tinny speakers!"
Re:Clever move, but late (Score:3, Insightful)
Re:Clever move, but late (Score:2)
Re:Clever move, but late (Score:2)
Re:Clever move, but late (Score:2)
Which is exactly what Microsoft has yet to figure out with the PocketPC line, and Palm has always known. Yet they do need to advance the product beyond a single-tasking 33 MHz device. A VGA screen would make some tasks far easier (an address book not being one of them). For PowerPoint, you're not going to use the device to show PowerPoint slides. You can't croud everyone around a 3" screen. But you CAN use it as your remote control for the slides, with a real time display and your own notes. For that, a better screen/processor does come in useful.
Incremental improvement as they are able to do it RIGHT is what Palm (and most of its licensees) have been good at, and they need to keep that up. They just need to get it right a little faster to keep the MHz kiddies (who run IT departments) happy.
Re:Spinning off an OS division. What about BeOS? (Score:1)
I'm sure Palm doesn't want the whole BeOS effort to go to waste, and now that they'll have a "separate" division for OS development, they need not be tied to just developing PDA operating systems. They can even try going towards IAs more, just as Be wanted to do.
On the other hand, I guess this would technically free up Palm's hardware division... they would probably be able to recover more market share by using other OS's instead of PalmOS on some models. I doubt they would want to, but it seems that this leaves the possibility open.
Re:Spinning off an OS division. What about BeOS? (Score:3, Informative)
As for BeOS itself, check out http://www.befaqs.com/save or http://www.beunited.org . There are efforts to get Palm to license BeOS itself (which they have no intention of using, they only bought the Be Engineers remember? so they could build a new PalmOS).
Hasn't this always... (Score:2, Insightful)
Re:Hasn't this always... (Score:2)
So what are they going to do? (Score:2, Funny)
Re:So what are they going to do? (Score:1)
Wow (Score:2)
Not sure if that was a wise choice, leaving ATT Labs [att.com]... They have some sweet projects. In fact im using VNC [att.com] right now. Thou a 650K a year, damn...
The future of handhelds (Score:1, Troll)
I predict that within two years, every Palm-like device will be running embedded Linux. The advances in CPU power, embedded-friendly features (can you say realtime scheduling), portability, and ease of development will make PalmOS (still stuck in the 90's) and WinCE (never a serious contender anyway) very unattractive, expensive options. As margins fade away and manufacturers look for ways to gain an edge on the competition, Linux will have the clear advantage from the cost perspective. Additionally, Linux-based devices are very popular amongst the technical crowd because of their configurability and stability (especially when compared to other embedded OSs like QNX), which will help prop up sales when the number of rich MBA-types dwindle.
Don't forget, also, that KDE is approaching its 3.0 release and the embedded version is gaining in popularity. I won't be surprised at all if it becomes a serious contender for PDA and cell phone desktops. Porting KDE to PalmOS, WinCE, or QNX would cost some money - but on Linux, it's practically native.
-CT
Re:The future of handhelds (Score:2, Funny)
You mean the Grafiti on the wall?
*rimshot*
Re:The future of handhelds (Score:1)
Unless the embedded QT gets released under the GPL, it will take quite some time and/or investment before any of the Linux GUI's will be able to run in an embedded system. On a normal desktop machine running linux X11 is responsible for converting all the nifty QT function calls to the nitty-gritty details of individual pixels on the screen. X11 is simply too much of an memory hog, and to feature rich to run on any of the current generation of palm-sized devices.
Also, most of the Gnome/KDE software is bloated beyond belief when seen from the standpoint of an embedded SW engineer, so there are still quite a long way before WinCE and PalmOS are obsoleted.
Re:The future of handhelds (Score:1, Informative)
-jim
Re:The future of handhelds (Score:1)
Re:The future of handhelds (Score:1)
But while we move on towards
the merge of PDAs, PocketPCs and mobile devices in 3G (UMTS), power consumption becomes more and more important. No ordinary user wants to recharge the battery of his "super-device" every 6 hours. But the ordinary user would like to watch small movies and listen to mp3 (or the successors techs) on his phone-device.
So the "advances in CPU power" must also be
advances in power consumption.
A Palm of today needs much less power than a
PocketPC like the iPaq (running Linux).
A Palm of today is useable as a device you
carry around and is "always on" like a moblie phone. PocketPCs aren't as far as that currently.
So let's hope that CPU (ARM, mobile MIPS, mobile PPC) and display technologies improve so much that these "super-devices" of the next years are indeed running Linux/KDE? otherwise it's
time for other OS/solutions.
Re:The future of handhelds (Score:1)
I would be pleased if your scenario came true, for sure if it became mainstream. But do you think that's what Palm bought BeOS for?
KDE/Qt Embedded won't fly on Linux handhelds (Score:2)
Running Qt/Embedded has all sorts of disadvantages, however:
There are two predominant environments for writing GUI apps on Linux handhelds: FLTK and Java, both using X11 as the display server. I doubt anything else is going to catch on widely.
Re:KDE/Qt Embedded won't fly on Linux handhelds (Score:1)
2) Why the need for different toolkits?
3) Why the need for different toolkits?
(aside) Argh, Konqueror has gone into slow-mode again in text boxes...
Anyway, there is nothing stopping someone from writing an Exceed like X11 manager for QT embedded anyway.
I want that QNX PDA interface - that looked damn good.
On a PDA, a single, integrated, interface is the way to go. Palm, WinCE, EPOC all have it. The other necessary thing is good applications - maybe someone can shrink KOffice down into a PDA format? Palm and PocketPC both have a myriad of good applications for the PDA display format. Linux programmers need to start programming apps for 320x240 displays, and QT/Embedded sounds like a good place to start.
So you guys, instead of starting up "yet another text editor" or "yet another mp3 player" on sourceforge, why not do something new, and have "PDA format document editor" and "PDA format mp3 player"? PDAs in a couple of years will probably have 480x320 hi-res displays and 128MB of RAM anyway...
Re:KDE/Qt Embedded won't fly on Linux handhelds (Score:5, Informative)
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.
Qt/embedded is already the best choice (Score:3, Informative)
Running Qt/Embedded has all sorts of disadvantages, however:
You can't use X11 remote display for development on/for the handheld anymore.
Use VNC [trolltech.com] instead then. VNC is also much more useful than X once the palmtop is out in the wild - palmtops don't usually have constant network access when they're in your pocket, and VNC can detach and reattach easily to existing sessions, even if you change your IP address in the mean time. X requires a constant network connection or else the app that you're running over X dies.
You can't share the handheld screen between applications written in different toolkits anymore.
And this is a bad thing? Personally I'd be very happy to see embedded Linux not making the same usability mistakes that desktop Linux has in the past, and which it is only now recovering from. Lots of toolkits == inconsistent interface == usability problems. Diversity is great, but there are places where it is inappropriate, and user interface is one of them. Not to mention the bloat aspect of having multiple toolkits...
You are tied to a single toolkit for handheld development.
See above.
Don't forget that Qt/embedded is also API-compatible with Qt/X11, which means that porting Qt apps from the Linux desktop is a cinch - and that's how Opera and Konq/e have been so rapidly successful - they are both based on Qt. Don't underestimate the importance of having a good browser for a palmtop. The only browsers I've seen for X11 that are optimized for display on a small palmtop screen are... Opera and Konq/e. You might as well run them under Qt/embedded.
How many full-blown browsers do you know written in FLTK or Java? Maybe when there's a nice tiny browser for FLTK using Gecko as a rendering engine there'll be something to talk about.
As for size, well, perhaps TinyX+FLTK+Blackbox really is no bigger than Qt/e. But think about what you get with Qt - Signals and Slots, a fast and very powerful canvas widget, full-blown Unicode support, in fact, all the nice features that have made Qt a huge success on the desktop. And, as I've said above, porting the multitude of existing Qt desktop apps is a no-brainer. Not to mention of course that the superb QPE is available, so if you want a complete environment for your users, it's just a compile away. No additional coding required.
FLTK doesn't offer any of this. In fact, no current X11 toolkit other than Qt itself offers all this. If you start adding other toolkits on top of TinyX then you can make up for some of the more important features... but oops, there goes your size, and your consistent interface.
If you have political problems with Qt, then say. You certainly seem to be short on valid technical problems.
Re:Qt/embedded is already the best choice (Score:2)
Linux has been a booming success with X11 as its graphics system and its wide variety of available GUIs. Anybody who wants any more consistency under X11 than they get with the standard conventions only has to restrain their urge to install packages whose GUI they don't like. All this talk about "inconsistency" and "usability" is just that: empty talk from people with an agenda to push, or people who value looks over functionality.
If you have political problems with Qt, then say. You certainly seem to be short on valid technical problems.
I would have a "political problem" with Qt/Embedded if I thought there was a chance that it might succeed and in the process do damage to Linux on handhelds. But I simply think Qt/Embedded is doomed (although we may see some Qt/X11 applications on handhelds still). The only thing that is marginally regrettable is that some people in the open source community waste effort on it, but if they don't get the issues, maybe they wouldn't help on other projects anyway.
Re:The future of handhelds (Score:1)
BTW nice restyle trolltech!
furthermore: on www.handhelds.org [handhelds.org] there are some really promising distros for ARM based PDAs
and finially a real beauty: Pocketlinux!! [pocketlinux.com] a verty nice distro!!!!
I really can't wait to try these distros on palm hardware!!!
Re:The future of handhelds (Score:2, Interesting)
Why? WinCE wasn't trying to be a handheld. It is trying to be a slimmed down version of a desktop OS. While it does enable some interesting ports (I'm still waiting for a port of Perl to the Palm (what a tounge twister!)) for a lot of PDA use (calander, to-do list, contacts, quick notes), it isn't the right model.
Palm, on the other hand, seems to do better. Perhaps Linux would with the right mix of apps, but I simply don't see it scaling that way and fitting into the day-to-day life of the average user.
Perhaps, instead, it will be a third (or, in this case, fourth) thing all together. Are there any serious PDA OSs out there aside from Palm and WinCE?
If I owned BeOS (Score:3, Funny)
Unfortunate for us Palm users (Score:2, Interesting)
#1 - Having the OS and hardware made by the same company is IMHO part of what has kept the Palm stable enough to be useable in a "if this crashes with my [flight information / meeting notes / date's phone number] in it, I'm screwed" sort of way. As Apple has shown, there are definite advantages to having the hardware and software guys on the same team.
#2 - As anyone who's dealt with Windoze will attest, the "it's their fault" / "no its THEIR fault" blame shifting that goes on between software and hardware vendors whenever a conflict comes up can only mean one thing: much longer waiting times before issues are resolved. With present-day Palm, like with Apple, we the consumer can say "your problem, you fix it!" and, while they may not fix it, they at least have to acknowledge that, hardware or software, its their company's problem and not some other company's problem.
#3 - Dilution of the OS. The Palm OS works as well as it does because it is purpose built. I daresay Win CE has, as one of its many faults, the "all things to all people" problem, which makes it bloated and cumbersome and all that. Once a seperate company owns the Palm OS, logically they would seek to expand it across as many different pieces of hardware as possible, to maximize revenue and marketshare. As the OS is rewritten to run on more and more things, it moves away from the original "here's the OS we wrote to run on this one little machine" and closer to "here's a Windows CE competitor. Hey Bill! Come and crush us!".
Obviously, I'm no expert. But its food for thought.
Re:Unfortunate for us Palm users (Score:2)
Yeah, because my Handspring was made by Palm...just like the Sony is, and the TRGPro, and the Handera...
There are about half a dozen PalmOS hardware companies out there, only one also makes hardware.
Yes, there are. Palm gave them up about three years ago.
Re:Unfortunate for us Palm users (Score:2)
2. I think Handspring, Sony, and TRG (HandEra) have shown that they can make their hardware work with PalmOS quite nicely.
3. I agree wholeheartedly. PalmOS is great at what it does, but I want more. I want proper networking. I want always on secure wireless access to email and other business apps. I want a higher res color screen (thank you Sony).
The NEEDS of the many, who just wanted an organizer were met by Frankin with their electronic Rolodex address book and calendar. The WANTS of the many are not yet addressed.
This could be great news (Score:2, Informative)
One project I was investigating recently was to see whether I could replace the default HotSync mechanism with a dynamically compressed XML-RPC connection so that systems could connect to the Palm across the Internet, and vice versa, thus obviating the whole PC HotSync requirement. I eventually lost enthusiasm for it, though, given the huge task of reimplementing the same mechanisms used by the HotSync subsystem, without the benefit of OS source.
Maybe if they Open Source it, I might reinvestigate doing it.
Re:This could be great news (Score:2)
I don't follow your logic?
It seems to me an OS (Operating System, not to be confused with Open Source) spin-off would make it LESS likely that the OS would go Open Source. For a combined company, a case could be made that Open Source helps make the OS more bug free, and thus the product gets better, thus more HW is sold...
If the company's whole business model revolves around OS licensing, on the other hand, things are very different. Just as one example, Handspring, Sony, etc are now free to use the code (varies by license, but in general..) as long as they publish their changes... And the OS is way too simple for the end-user for downline 'support' to be an option for making money...So how do they stay in business?
Re:This could be great news (Score:1)
Instead implementing something like SyncML would make sense.
Re:This could be great news (Score:1)
I agree with you though that an XML-RPC wouldn't be the fastest system, but with some form of dynamic zip compression, you could reduce the transmission size dramatically.Especially for table access, the ability to zip up the stream, coupled with textual conversion of data, could provide significant compression of duplicated data across multiple records.
Paul.
BeOS - CE? (Score:2)
Maybe they're going to reduce the BeOS kernel into something that runs on a Palm Pilot. I thought on the same token, Win CE is based on Win NT.
One might hope for a BeOS desktop and palmtop along the same lines as Windows.
Just a thought.
Re:BeOS - CE? (Score:1)
PDAs are like desktop operating systems, except the apps run in a fullscreen window all of the time instead of a randomly sized window. A 206MHz StrongARM (or 400MHz XScale) will be easily able to emulate a Palm Pilot at full speed, so forget about API and binary compatibility.
Of course, I can't wait for the dual-processor PDAs.
No Linux in Sight (Score:5, Insightful)
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.
Re:No Linux in Sight (Score:2)
No, Linux is originally Linus's terminal emulator project. Then it was a replacement for Minix, a free Unix operating system that people could run on widely available, inexpensive desktop hardware. And in that role, it was primarily used first as a desktop box; only later (think post 1.0) were people starting to deploy it widely as a server platform.
Also, some Linux platforms run XIP. It's fairly easy to make the kernel itself run in place on linear ROM; just a few linker script tweaks. The Linux VR kernel also supports XIP for chosen exectuables and shared libraries, thanks to Rob Leslie's work on XIP for cramfs. On a file by file basis, you get a choice between uncompressed execute-from-ROM via MMU, or cramfs's block-by-block compression for executables you don't expect to be paged in as much.
Yes, Unix systems tend to think of the world in terms of files. But for specific, chosen access styles, under the hood the files can be accessed just as efficiently as a fileless PalmDB scheme. Unix gives you a choice of how to do it, and you're not stuck with it; you can still read() and write() to files you're usually treating as memory-mapped databases. (With whatever synchronization you deem necessary; PalmOS doesn't have concurrent access synchronization problems because it, like DOS, only supports one program running at a time.)
Actually, WinCE has support for XIP as well, but I don't know enough about it to post anything authoritative.
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.
Like this? [agendacomputing.com]
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.
In other words, desktop Linux people should give up because a) you can't just throw a Windows or Mac executable on any machine and expect it to work. In fact, Apple should give up as well.
Nah. Diversity is a good thing. It's what got Linux here. It's what got *BSD here. We wouldn't have Gnome or KDE if they hadn't decided to dump Motif and Athena.
Re:No Linux in Sight (Score:2)
Like this? [agendacomputing.com]
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.
Yep, exactly like that. Now also look at http://www.linuxda.com/ [linuxda.com]. Both are Palm-like Linux-based PDAs. I'll lay you odds that you can't beam an executable from one to the other and have it work without recompiling. (For one thing, the Agenda uses a MIPS processor, the PowerPlay III uses Dragonball.) That may be great for darwinism, but not for selling units. Not in the handheld space.
Old News (Score:2)
Three fourths of News is New.
Kind-of stale news. (Score:2, Informative)
Incidentally, let's all hope that they drop the Newco moniker.
What about Micro$oft? (Score:2)
Psion did this too... (Score:2)
Psion did this with their OS (EPOC). The OS was transferred to Symbian. The idea was to let other companies such as Nokia, Ericsson, Motorola, etc use the OS in their new mobile phones. I don't think they were successfull. Motorola cancelled their product...
Now Psion has stopped making new PDAs using EPOC. PocketPC seems to be the winner here.
I really hope that Palm does not go the same route. If PalmOS looses market share, would Palm simply make a PocketPC-based PDA with some simple apps for migrating from PalmOS?
Re:Psion did this too... (Score:2)
Oh, and Sanyo recently showed a PDA running Epoc (Quartz 6.1) vs the one they've shown before (Quartz 6.0) so I fail to see your point
Why did they spin *THIS* part off? (Score:3, Interesting)
Why does Palm think they're about to, in any way, create a new hardware device that they think will surpass these existing innovative devices? Palm is ALWAYS behind the curve on hardware advances in this area. We're not even talking about comparing them to the iPAQ [handhelds.org], VTech Helio [myhelio.com], Agenda [agendacomputing.com], Yopy [yopy.com], and the other dozens of non-PalmOS, non-WinCE handheld PDA devices.
Currently, Palm's OEMs for the PalmOS® software include:
They get licensing from each and every one of these OEMs. Their hardware is the last thing to ever be updated. It is without a doubt, the least innovative portion of their business.. and they're choosing to keep it?!
I don't quite understand the motive behind this decision on their part. I suppose I'll find out at Palmsource [palmsource.com] in February.
Re:Why did they spin *THIS* part off? (Score:2)
Well to be honest the m500s as much as you seem to dislike it really is a close run with Handspring's product.
I had one of the first Visors (pre-order, wait list, blah-blah). None of the springboards was every well priced. I waited for over a year for a GPS and finally gave up. The MP3 springboards cost more then stand alone players (almost twice what I payed for the Rio). The 6-in-1 was more then two years late last I looked. The only thing I ever got was the backup module, which isn't that much more useful then frequent hot syncing.
Still I think the slot is cool, so when I went busted the Visor Handspring's new products were high on my list. I eventually decided I liked the Visor Edge. The m505 was a little smaller, barely heaveyer, and had a vibrating alarm, oh and a tiny slot for extra memory (the Edge requires a large plastic holder). The thing that finally convinced me to get the Edge is the metal cover (vs. the 505's psudo leather). Since I broke the Visor by breaking it through the plastic cover, I liked the idea of something a bit more sturdy.
Of corse if I had been looking for color Handspring had nothing. The m515, or whatever Palm's color m500 is pretty much has the market. It is the smallest little color PalmOS box.
That doesn't mean palm makes the best hardware all across the line, but they don't do so bad.
Re:Why did they spin *THIS* part off? (Score:2)
And a side note: Sony didn't invent VFS. Palm gave them an early release of their VFS APIs for the original CLIE in order to get them on board for the PalmOS. And TRG (now HandEra) had their own API for the TRGpro (their original device, with CF slot), which frankly was a lot faster. :-)
Spinning off its OS devision. DEVISION? (Score:1)
that bad? (Score:2)
Why? (Score:1, Interesting)
Every time Edison came up with a new invention, he didn't spin it off into it's own company. Everything remained the product of Edison General Electric, or one of it's divisions. Same thing goes for IBM. Ford hasn't spun each model into it's own company.
How are you supposed to build a large business if you keep giving away all your best products?
Re:Why? (Score:1)
Re:Why? (Score:1)
A bad businessman couldn't do that. Edison General Electric went on to form the core of GE, along with several other, smaller companies.
Re:Why? (Score:1)
AT&T and HP did this recently. AT&T broke itself into AT&T, Lucent and NCR. Then the new AT&T spun off AT&T Wireless. HP broke itself into a new HP (computers, printers) and Agilent (test equipment, which was the original business).
No wonder (Score:1)
+ stock options + bonuses + grants.
No wonder these guys take decisions which dont seem intelligent to us normal guys.
No wonder they, sometime, miss things which seem so obvious to many.
YASO (Score:2)
Lets not forget... (Score:2, Insightful)
Apple should have spun off MacOS long ago... (Score:1)
It's a little known fact that a skunkworks Apple project known as Star Trek succeeded in porting MacOS to run on an x86 system. Instead of embracing it, Apple management killed off the project fearing it would have a detrimental impact on Apple hardware sales.
If MacOS had been spun off into a seperate entity, they would have had no such restrictions on their behaviour, and x86 MacOS would have been released. A far superior product to Windows at that time. The world might have looked a lot different if the Star Trek project had not been killed.
By spinning off PalmOS into a seperate company which doesn't care who it sells licences to, Palm will end up encouraging other players to create devices that run PalmOS, because they know that the Palm hardware arm no longer has an "inside advantage" over them. It will also likely speed ports of PalmOS to other platforms, increasing market acceptance of the Palm platform.
Regards,
jc
Palm Software, alone again (Score:2, Informative)
The Zoomer used a V20 CPU and had 1MB of ram and 4MB of rom. It had stroke-based handwriting recognition (a first in portable devices) and a GREAT selection of bundled apps, including a 20 language translator (which didn't have a word for "computer" in it, oddly - it would come in handy when trying to explain what the hell you were scribbling on) and a currency converter - Imagine that!
The software was PC-GEOS, with basically three new things; An updated digitizer driver to support the input method, a new CGA driver to support a 384 wide by 512 high mono CGA display, and handwriting recognition. It was at least as stable as PalmOS with a hack or two, and had a whole hell of a lot more bundled software. I don't remember what kind of expansion it had, I seem to recall it took Type 2 flash cards from sandisk. I think I had a 1.8 MB card.
Anyway, I mention it because it was Palm's first job, they did the GEOS and apps bundle for it. It was actually a pretty cool little device, and it's also where Graffiti, the PalmOS' input method came from; Graffiti was originally an upgrade for the Zoomer. You loaded it and it created a little box you drew your characters in. The Zoomer's text input was done all over the screen. Graffiti differs from the original handwriting recognition largely in that there are no multi-stroke characters.
So now they're "spinning off" the software division? Big shock. They worked well as an independent company; Now that there's quotes around that, they should at least be able to get most of their efficiency going again. I refuse to speculate on any Be issues, though.
Side note; You can put GEOS on a GRiDPad 1710, and use the version of Graffiti from the Zoomer on it. I know this because I've done it. I need to make up some new battery packs for my GRiDPad, though. I'd really like to have it available while I work on my car, so I can take notes and whatnot. It's got a big (640x400x1bpp) monochrome CGA display, which is supported by GEOS' default CGA driver, a tethered pen which is actually better for industrial use because you can't lose the damn thing, and a nice, bright backlight. Hell, I've found my keys by that backlight before.