Quote:
|
Originally Posted by macrotor
It appears my lingo may be inaccurate on how the POS divides up the processes in the background. From the sounds of it, the OS chooses what tasks can be combined and which need to run on a separate thread, hence optimizing the overhead.
|
I wish!
The current Cobalt is not
nearly that good. That is, however, the kind of thing we are moving towards... though the main intent is to divide and combine
processes dynamically. What is inside of Cobalt today includes a lot of the technology that will enable this, we just aren't to the point of making full use of it.
Quote:
|
Originally Posted by macrotor
My point was that the current architecture of POS5 seems similar to the old Mac days in that a poorly-programmed application can monopolize all processing and RAM, and then crash the entire device if it glitched. The device is at the mercy of proper programming. Also, any multi-tasking is limited to what the programmer implements.
|
Oh yeah, absolutely. For the most part, that is no longer an issue in Cobalt. Because of the underlying support for protected memory and multithreading, if an application crashes we can catch it and recover as on a PC, and likewise if the application has become unresponsive we put up a dialog saying so and giving the user a chance to kill it.
Quote:
|
Originally Posted by macrotor
Once again, thanks for stopping by!
|
You're very welcome, I hope it is useful!