Linked by Thom Holwerda on Wed 30th Jan 2013 23:06 UTC
PDAs, Cellphones, Wireless And so, today, RIM announced its Hail Mary - a brand new mobile operating system (well, sort-of new), as well as two new devices. In addition, the Canadian company also officially changed its name from Research In Motion to Blackberry. The first few reviews of Blackberry 10 are already out, and it's not bad. The problem, however, is that in the case of Blackberry, 'not bad' could easily mean 'not good enough'.
Thread beginning with comment 551037
To read all comments associated with this story, please click here.
Wishy Washy What?
by Lobotomik on Thu 31st Jan 2013 14:55 UTC
Lobotomik
Member since:
2006-01-03

None of that wishy-washy My First Multitasking that many other platforms employ because they're all server-class operating systems shoved into a mobile device, but the real deal, made possible because of QNX' embedded origins and focus

Are you serious? In what way is Android's multitasking wishy-washy (whatever wishy-washy means)? In what way is QNX going to make it any better? What could you do with PocketPC that you cannot do with Android? Just why Server Class Operating Systems are going to multitask worse than an Embedded OS?

If you leave an application running, it will consume power be it with PocketPC, Android, QNX or with no OS at all. RAM will fill up as users launch more apps. So huge numbers of man hours have been put in teaching these OS's when to freeze apps to save battery, and when to evict apps from RAM, without pissing of the user. Of course, some have been more successful than others, in different metrics (some multitask better, or save more power, or need less resources, or piss off the users less). How QNX/BBOS10 will fare remains to be seen, but it does not need to be any better or worse than the others.

Reply Score: 2

RE: Wishy Washy What?
by Neolander on Thu 31st Jan 2013 18:20 in reply to "Wishy Washy What?"
Neolander Member since:
2010-03-08

None of that wishy-washy My First Multitasking that many other platforms employ because they're all server-class operating systems shoved into a mobile device, but the real deal, made possible because of QNX' embedded origins and focus

Are you serious? In what way is Android's multitasking wishy-washy (whatever wishy-washy means)? In what way is QNX going to make it any better? What could you do with PocketPC that you cannot do with Android? Just why Server Class Operating Systems are going to multitask worse than an Embedded OS?

If I can speak for myself... The fact that Android and iOS can randomly close background apps at any moment, without having their state swapped out to mass storage first, is a major design mistake. If QNX can manage to avoid this outcome in some way, it will already have done mobile multitasking a favor.

And it is also true that anything Linux, NT or BSD-based tends to be quite bad at task prioritization, with things easily getting sluggish as soon as some combination of heavy processing and disk IO is going on in the background. The very reason why RTOSes like QNX exist is so as to avoid this kind of issues, because car brakes cannot afford to respond more slowly when the onboard GPS is busy updating the onscreen map...

Edited 2013-01-31 18:23 UTC

Reply Parent Score: 3

RE[2]: Wishy Washy What?
by mkone on Thu 31st Jan 2013 23:14 in reply to "RE: Wishy Washy What?"
mkone Member since:
2006-03-14

If I can speak for myself... The fact that Android and iOS can randomly close background apps at any moment, without having their state swapped out to mass storage first, is a major design mistake. If QNX can manage to avoid this outcome in some way, it will already have done mobile multitasking a favor.


I am sure that is by design. If the OS makes no guarantees that it won't forcibly close your app if it needs the resources for apps and tasks in the foreground, or indeed guarantees that it will forcibly do so, then developers will not be tempted to code apps that need to be run in the background. At least those paying attention won't be.

Reply Parent Score: 3

RE[2]: Wishy Washy What?
by Nelson on Fri 1st Feb 2013 05:22 in reply to "RE: Wishy Washy What?"
Nelson Member since:
2005-11-29

I sure hope they do.

Windows 8 handles this by putting apps into a suspended state and expecting state saving to go on during that transition.

From there apps are either returned to "Running" state at some point in the future, or killed.

If your app was killed when it next resumes, you load state, if your app was suspended, then there's no need to reload state as it is still resident in memory.

I hope BB does something similar.

Reply Parent Score: 3

RE[2]: Wishy Washy What?
by Lobotomik on Fri 1st Feb 2013 10:51 in reply to "RE: Wishy Washy What?"
Lobotomik Member since:
2006-01-03

Android is designed from day One to keep the state of applications frozen when they are kicked out, so they can be revived later with their memories intact.

The application has to cooperate in selecting what it absolutely needs to remember before being frozen (like, the browser might get by with something like the current URL and a position in it, rather than the many megs taken up by the rendered page). I am sure BBOS10 will do much the same, with much the same limitations.

Huge applications like comples games might have a hard time being minimized, and might be thrown away completely when their resources are needed. Or not, that depends on their design. That might be what you experience as "bad multitasking", but there is no easy way around it.

Other than that, the OS can shove the entire address space of a frozen app to mass storage, but that will fill up mass storage very fast, will be very slow, and will probably eat up a lot of battery, and still the app must be designed to be stopped and restarted at any time.

When free resources are gone, used resources must be freed. If the user does not do it himself, the OS has to choose. Once it has disposed of the dispensable (by letting the app choose what to keep), it will have to dispose of the indispensable (by killing old apps in the background).

So, I don't expect much advancement in BBOS10 multitasking. What's done in Android (and possibly in Winphone) is close to the best you can do when you have little or no virtual memory and you don't want to force users to close their applications manually whenever they finish working with them.

Reply Parent Score: 2