MikeTheC
Nov 25, 10:46 PM
All this talk about Palm needing to modernize their OS, or it is outdated, or needing to re-write is absolutely hilarious.
On a phone, I want to use its features quickly and easily. When I have to schedule an appointment, I want to enter that appointment as easily as possible. When I want to add something to my to-do list, I want to do it easily and quickly. And first and foremost, I want to be able to look up a contact and dial it as quickly as possible.
A phone is not a personal computer. I couldn't care less about multitasking, rewriting, "modern" OSes (whatever "modern" means). "Modern" features and look is just eye candy and/or toys. A mobile phone is a gadget of convenience, and it should be convenient to use. Even PalmOS 1.0 was convenient. It was just as easy to use its contact and calendar features as any so-called "modern" OS is today.
I would really like to know how "modernizing" the OS on my phone would help me look up contacts, dial contacts, enter to-do list entries, and entering calendar entries any better that I could today.
Again, I repeat: a phone is not a personal computer. There's no point in treating it as such.
The same point could largely be made about cars, but I don't think either of us would want to be driving a Model T or Model A Ford these days, would we?
The term "Modern" as applied to operating systems has little to do with the interface per se. It primarily concerns the underpinnings of the OS and how forward-looking and/or open-ended it is. Older operating systems, if you want to look at it in this way, were very geared to the hardware of their times, and every time you added a new hardware feature or some new kind of technology came out, you wound up making this big patchwork of an OS, in which you had either an out-dated or obsolete "core" around which was stuck, somewhat unglamorously, lots of crap to allow it to do stuff it wasn't really designed for. Then, you wound up having to write patches for the patches, etc., ad infinitum.
Apple tried to go the internal development route, but that didn't work because their departmental infrastructure was eating them from the inside out at the time and basically poisoned all of their new projects. They considered BeOS because it was an incredibly modern OS at the time that was very capable, unbelievably good at multitasking, memory protection, multimedia tasks, etc. However, that company was so shaky that when Apple decided not to go with them, they collapsed. One of the products which was introduced and sold and almost immediately recalled that used a version of BeOS was Sony's eVilla (you just have to love that name -- try pronouncing it out loud to get the full effect).
Ultimately, they went with NeXT's BSD- and Mach-Kernel-based NeXTStep (which after a bunch of time and effort and -- since lots of it is based on Open Source software, there were a healthy amount of community contributions to) and hence we now have Mac OS X.
I'll leave it to actual developers and/or coders here to better explain and refine (and/or correct) what I've said here, should you wish greater detail beyond what I am able to -- and therefore have -- provided above.
The whole point of going with a modern OS implemented for an imbedded market (i.e. "Mac OS X Mobile") is it gives you much more direct (and probably better implemented and/or better-grounded) access to modern technologies. Everything from basic I/O tasks that reside in the Kernel to audio processing to doing H.264 decoding to having access to IPv4 or IPv6, are all examples of things which a modern OS could do a better job of providing and/or backing.
From what I understand, PalmOS is something that was designed to first and foremost give you basic notepad and daily organizer functionality. When they wrote, as you say, PalmOS 1.0, they happened to implement a way for third parties to write software that could run on it. This has been both a benefit and a bane of PalmOS's existence. First off, they now have the same issues of backwards-compatibility and storage space and memory use/abuse that a regular computer OS has. I said it was both a benefit and a bane; but there's actually two parts to the "bane" side. The first I've already mentioned, but the second is the fact that since apps have been written which can do darn near any conceivable task, people keep wanting more and more and more. And this then goes back to the "patchwork" I described earlier in talking about "older" computer OSs.
Then people want multimedia, and color screens, and apps to take advantage of it, and they want Palm to incorporate DSPs so they can play music, and of course that brings along with it all of the extra patching to then allow for the existence of, and permit the use of, an on-board DSP. And now you want WiFi? Well, shoot, now we gotta have IPv4 as well, and support for TCP/IP, none of which was ever a part of the original concept of PalmOS.
And even if you don't want or need any of those features in your own PDA, I'm sorry but that's really just too bad. Go live in a cave if you like, but if you buy a new PDA, guess what: you're gonna get all that stuff.
And at some point, all of this stretches an "older" OS just a bit too far, or it becomes a bit absurd with all the hoops and turns and wiggling that PalmOne's coders have to go through, so then they say, "Aw **** it, let's just re-write the thing."
Apple comes to this without any of *that* sort of legacy. Doubtless there will be no Newton code on this thing anywhere, but what Apple's got is Mac OS X, which means they also have the power (albeit somewhat indirectly) of an Open Source OS -- Linux. And in case you weren't aware, there are already numerous "imbedded" implementations of Linux -- phones, PDAs, game systems, kiosks, etc. -- all of which are data points and collective experience opportunities which ALREADY EXIST that Apple can exploit.
So no, having a "modern" OS is not a bad thing. It's actually a supremely awesome thing. What you're concerned about is having something that is intuitive AND efficient AND appropriate to the world of telephone interfaces for the user interface on the device you'd go and buy yourself.
All I can say, based on past performance, is give Apple a chance.
Now, here's a larger picture thought to ponder...
If Apple goes to market with the iPhone, then this is going to open up (to some extent) the viability of a F/OSS community cell phone. And this is a really good thing as well because it represents a non-commercial, enthusiast entrance into what up until now has been a totally proprietary, locked-down OS-based product world. It has the potential to do to cell phones what Linux has inspired in Mac OS X.
On a phone, I want to use its features quickly and easily. When I have to schedule an appointment, I want to enter that appointment as easily as possible. When I want to add something to my to-do list, I want to do it easily and quickly. And first and foremost, I want to be able to look up a contact and dial it as quickly as possible.
A phone is not a personal computer. I couldn't care less about multitasking, rewriting, "modern" OSes (whatever "modern" means). "Modern" features and look is just eye candy and/or toys. A mobile phone is a gadget of convenience, and it should be convenient to use. Even PalmOS 1.0 was convenient. It was just as easy to use its contact and calendar features as any so-called "modern" OS is today.
I would really like to know how "modernizing" the OS on my phone would help me look up contacts, dial contacts, enter to-do list entries, and entering calendar entries any better that I could today.
Again, I repeat: a phone is not a personal computer. There's no point in treating it as such.
The same point could largely be made about cars, but I don't think either of us would want to be driving a Model T or Model A Ford these days, would we?
The term "Modern" as applied to operating systems has little to do with the interface per se. It primarily concerns the underpinnings of the OS and how forward-looking and/or open-ended it is. Older operating systems, if you want to look at it in this way, were very geared to the hardware of their times, and every time you added a new hardware feature or some new kind of technology came out, you wound up making this big patchwork of an OS, in which you had either an out-dated or obsolete "core" around which was stuck, somewhat unglamorously, lots of crap to allow it to do stuff it wasn't really designed for. Then, you wound up having to write patches for the patches, etc., ad infinitum.
Apple tried to go the internal development route, but that didn't work because their departmental infrastructure was eating them from the inside out at the time and basically poisoned all of their new projects. They considered BeOS because it was an incredibly modern OS at the time that was very capable, unbelievably good at multitasking, memory protection, multimedia tasks, etc. However, that company was so shaky that when Apple decided not to go with them, they collapsed. One of the products which was introduced and sold and almost immediately recalled that used a version of BeOS was Sony's eVilla (you just have to love that name -- try pronouncing it out loud to get the full effect).
Ultimately, they went with NeXT's BSD- and Mach-Kernel-based NeXTStep (which after a bunch of time and effort and -- since lots of it is based on Open Source software, there were a healthy amount of community contributions to) and hence we now have Mac OS X.
I'll leave it to actual developers and/or coders here to better explain and refine (and/or correct) what I've said here, should you wish greater detail beyond what I am able to -- and therefore have -- provided above.
The whole point of going with a modern OS implemented for an imbedded market (i.e. "Mac OS X Mobile") is it gives you much more direct (and probably better implemented and/or better-grounded) access to modern technologies. Everything from basic I/O tasks that reside in the Kernel to audio processing to doing H.264 decoding to having access to IPv4 or IPv6, are all examples of things which a modern OS could do a better job of providing and/or backing.
From what I understand, PalmOS is something that was designed to first and foremost give you basic notepad and daily organizer functionality. When they wrote, as you say, PalmOS 1.0, they happened to implement a way for third parties to write software that could run on it. This has been both a benefit and a bane of PalmOS's existence. First off, they now have the same issues of backwards-compatibility and storage space and memory use/abuse that a regular computer OS has. I said it was both a benefit and a bane; but there's actually two parts to the "bane" side. The first I've already mentioned, but the second is the fact that since apps have been written which can do darn near any conceivable task, people keep wanting more and more and more. And this then goes back to the "patchwork" I described earlier in talking about "older" computer OSs.
Then people want multimedia, and color screens, and apps to take advantage of it, and they want Palm to incorporate DSPs so they can play music, and of course that brings along with it all of the extra patching to then allow for the existence of, and permit the use of, an on-board DSP. And now you want WiFi? Well, shoot, now we gotta have IPv4 as well, and support for TCP/IP, none of which was ever a part of the original concept of PalmOS.
And even if you don't want or need any of those features in your own PDA, I'm sorry but that's really just too bad. Go live in a cave if you like, but if you buy a new PDA, guess what: you're gonna get all that stuff.
And at some point, all of this stretches an "older" OS just a bit too far, or it becomes a bit absurd with all the hoops and turns and wiggling that PalmOne's coders have to go through, so then they say, "Aw **** it, let's just re-write the thing."
Apple comes to this without any of *that* sort of legacy. Doubtless there will be no Newton code on this thing anywhere, but what Apple's got is Mac OS X, which means they also have the power (albeit somewhat indirectly) of an Open Source OS -- Linux. And in case you weren't aware, there are already numerous "imbedded" implementations of Linux -- phones, PDAs, game systems, kiosks, etc. -- all of which are data points and collective experience opportunities which ALREADY EXIST that Apple can exploit.
So no, having a "modern" OS is not a bad thing. It's actually a supremely awesome thing. What you're concerned about is having something that is intuitive AND efficient AND appropriate to the world of telephone interfaces for the user interface on the device you'd go and buy yourself.
All I can say, based on past performance, is give Apple a chance.
Now, here's a larger picture thought to ponder...
If Apple goes to market with the iPhone, then this is going to open up (to some extent) the viability of a F/OSS community cell phone. And this is a really good thing as well because it represents a non-commercial, enthusiast entrance into what up until now has been a totally proprietary, locked-down OS-based product world. It has the potential to do to cell phones what Linux has inspired in Mac OS X.
0 comments:
Post a Comment