Exactly, a far better graps of what they intented it to do - not Apple, to which they need to ad hoc submit now (well, not that they wouldn't need to do it in one alternative apporach I roughly described - but less, mostly just under "does this behave properly?")
The simple fact of the matter is that much fuller multitasking is available and works fine. There's plenty of "square holes"; it's your problem if you try to excuse one limited, forced approach.
Yeah, that's probably also how I got to know about the mechanism in whales, I think.
Thing is - it's not exactly a matter of training, mostly a physiological response. One which I wouldn't be quick to consider as routine and safe in case of a human. But whales, sure.
You think developers have no means of predicitng if their apps might benefit from running in the background (if they fall under quite obvious categories), that they are unable to describe it for approval process? But...somehow will be able to recode their apps? (hell, code them in the first place)
Don't think in the confines of "new multitask states" with which you were apparently already spoon-fed. Some other platforms (no, Android is not the best example) do full multitasking just fine.
First, S40 is not Symbian (the latter is only 20% of what Nokia makes). Secondly, Nokia almost has a larger part of smartphone market than all the other players combined (where do you see strictly "technology" advances now anyway?)
But most importantly...well, I guess you think it's just horrible that Nokia focuses, for a long time, on as broad spectrum of the market as possible, right? Not only on "premium" people living in "premium" places, segment about which some manufacturers only care about; such a shame. That tends to spread resources. Nokia contributed greatly to close to 5 billion mobile subscribers that the world has now; for many of those people their first real means of communication, a great shift for humanity, that sort of "crap". Unfortunatelly - feelings and expectations of "investors" overlook such long term societal effects (a thing which will also bring new opportunities for "investments"...) - oh well, as long as they are comfortably profitable it's fine (and we'll see how some dispute ends up regarding possible freeriders on, also, Nokia R&D); BTW, not so breathtaking bottom line might be also because Nokia actually owns over a dozen of their manufacturing facilities, most of them not in China, half in the EU, and one even quite close to Cupertino. But I guess you think not outsourcing to sweatshops is also "fucked"...
Weren't there some Chinese "clones" already? Which might be the idea, and even more so for Symbian actually - it's probably the easiest and least expensive way, for many Chinese manufacturers, to have a full smartphone instead of weird sofware they offer now.
And shouldn't be that much of a problem - from what I heard people like to buy "original" anyway, if they can. But effects of scale might get interesting.
MS put self-imposed limits on what they want to view as their market anyway. 90%, sure; but that means a little over 1 billion PCs. A far cry from what mobile market is accomplishing.
Hence the place for default setting of not being suspended or closed, communicated from Appstore update, for apps/devs which requested that funcionality and were deemed worthy...
Well, while Qt dev environment for Maemo is available for Linux - if you want to target also Symbian (which generally will be a very good idea), it's...Windows only so far. So, yeah.
OTOH some of the targets might get interesting. There's a nice video of MeeGo tablet floating around, "netbooks" aren't out of the question. It might get some people away from their Win machine for a while; and so on.
Don't be too surprised by Symbian breaking this year the "100 million devices sold annually" barrier, and generally maintaining quite well its half of smartphone market. Nokia finally really started pushing it in the mainstream class.
So called "junk" also enables this, allowing very modestly priced devices with greast power management. And Symbian^4 has Qt as its main API.
You might call it apocalypse of the undead if you really wish to, but I would be suprised if Symbian won't remain a major player for a very long time. Plus zombies are cool.
Well, the specific implementation of Apple is beside the point here, really.
However...that list seems to demonstrate how what I desribe is actually more elegant. "Suspend that app" falls under #7; and #6 is even more straightforward of course. All of the rest boils down to "allow this nicely behaving app to consume max x percent of resources while in the background" anyway.
It doesn't matter what developer wants, it matters what customer wants.
It has some things nicely covered - enabling really inexpensive devices, squeezing a lot from what little resources they might have; or power management. And should get more pleasant with the shift to Qt.
"Symbian will still be used in low-end devices from Nokia, Samsung, and Sony Ericsson."
plus it's not going into low-end (that is the space of S30 and, more and more, S40), it takes over middle-range (which was coming for a few years; and is now very clear with devices like, say, Nokia 5230 - touchscreen smartphone with fully free (offline) turn-by-turn navigation for less than $150 without contract as of now; and it's not even the cheapest one)
Plus it might be really not such a big deal. After all, both MeeGo and Symbian are moving towards UI based on Qt, and using it as their main API for apps.
"Heavyweight" MeeGo backend will drive their "mobile computing" devices, while traditionally more lightweight (but also more limited / moving forward more intermittently) Symbian will be on on the mainstream bulk of affordable devices, still offering something pretty close.
It's what they are doing already. S40 still lives (actually, is the largest part of what Nokia sells, and the most popular mobile phone platform), still has a future. Even S30 ships quite a few units. The plan seemed to be from the beginning to have, top to bottom, MeeGo - Symbian - S40 - S30 lineup. In time, the price range of each category moves down.
Would it really be an issue? If whole things is suspended / doesn't need anything else - no problem. If it gets max few percent of CPU, after confirming it's not even very resource hungry in first place while it just sits there and does its job - also no problem. Plus hey, there could be always a way for users to change the default. Right now they have actually less choice.
Lifespan of iPhone is already artificially limited. With the current prices of flash, how small part of it mobile OSes actually need, and how large part of this storage is almost always static anyway, there shouldn't be much of a problem when FS is aware of the issue and rotates the space used as swap every now and then.
Symbian devices support virtual memory for some time now, and there was no wave of them suddenly starting to die.
They do happen "automagically" in real life. Take some old app made for Win3.11, run it on latest Win version which supports it (XP?) and voila! The app can nicely behave in a multitasking environment, no changes required.
It's just the way Apple chose to implement it exclusively. But there could also be, say, a scheduler giving very little amount of resources to some old apps, when they are in the background; with majority of old apps simply having their processes suspended. Wouldn't really require any code changes, just a setting carried over from the Appstore while updating to latest OS version / setting "suspend" by default / allowing for low resource usage while in the background after request by dev and confirmation by Apple that the app is something for which it makes sense (games? No... IM? Hell yeah!) and the app itself behaves nicely.
Slashdot Mirror
Exactly, a far better graps of what they intented it to do - not Apple, to which they need to ad hoc submit now (well, not that they wouldn't need to do it in one alternative apporach I roughly described - but less, mostly just under "does this behave properly?")
The simple fact of the matter is that much fuller multitasking is available and works fine. There's plenty of "square holes"; it's your problem if you try to excuse one limited, forced approach.
Yeah, that's probably also how I got to know about the mechanism in whales, I think.
Thing is - it's not exactly a matter of training, mostly a physiological response. One which I wouldn't be quick to consider as routine and safe in case of a human. But whales, sure.
Do you see something about "getting attached" in just being a steady customer for over a decade?
You think developers have no means of predicitng if their apps might benefit from running in the background (if they fall under quite obvious categories), that they are unable to describe it for approval process? But...somehow will be able to recode their apps? (hell, code them in the first place)
Don't think in the confines of "new multitask states" with which you were apparently already spoon-fed. Some other platforms (no, Android is not the best example) do full multitasking just fine.
First, S40 is not Symbian (the latter is only 20% of what Nokia makes). Secondly, Nokia almost has a larger part of smartphone market than all the other players combined (where do you see strictly "technology" advances now anyway?)
But most importantly...well, I guess you think it's just horrible that Nokia focuses, for a long time, on as broad spectrum of the market as possible, right? Not only on "premium" people living in "premium" places, segment about which some manufacturers only care about; such a shame. That tends to spread resources.
Nokia contributed greatly to close to 5 billion mobile subscribers that the world has now; for many of those people their first real means of communication, a great shift for humanity, that sort of "crap". Unfortunatelly - feelings and expectations of "investors" overlook such long term societal effects (a thing which will also bring new opportunities for "investments"...) - oh well, as long as they are comfortably profitable it's fine (and we'll see how some dispute ends up regarding possible freeriders on, also, Nokia R&D); BTW, not so breathtaking bottom line might be also because Nokia actually owns over a dozen of their manufacturing facilities, most of them not in China, half in the EU, and one even quite close to Cupertino. But I guess you think not outsourcing to sweatshops is also "fucked"...
Weren't there some Chinese "clones" already? Which might be the idea, and even more so for Symbian actually - it's probably the easiest and least expensive way, for many Chinese manufacturers, to have a full smartphone instead of weird sofware they offer now.
And shouldn't be that much of a problem - from what I heard people like to buy "original" anyway, if they can. But effects of scale might get interesting.
MS put self-imposed limits on what they want to view as their market anyway. 90%, sure; but that means a little over 1 billion PCs. A far cry from what mobile market is accomplishing.
Hence the place for default setting of not being suspended or closed, communicated from Appstore update, for apps/devs which requested that funcionality and were deemed worthy...
Well, while Qt dev environment for Maemo is available for Linux - if you want to target also Symbian (which generally will be a very good idea), it's...Windows only so far. So, yeah.
OTOH some of the targets might get interesting. There's a nice video of MeeGo tablet floating around, "netbooks" aren't out of the question. It might get some people away from their Win machine for a while; and so on.
Don't be too surprised by Symbian breaking this year the "100 million devices sold annually" barrier, and generally maintaining quite well its half of smartphone market. Nokia finally really started pushing it in the mainstream class.
So called "junk" also enables this, allowing very modestly priced devices with greast power management. And Symbian^4 has Qt as its main API.
You might call it apocalypse of the undead if you really wish to, but I would be suprised if Symbian won't remain a major player for a very long time. Plus zombies are cool.
Why not both?
Well, the specific implementation of Apple is beside the point here, really.
However...that list seems to demonstrate how what I desribe is actually more elegant. "Suspend that app" falls under #7; and #6 is even more straightforward of course. All of the rest boils down to "allow this nicely behaving app to consume max x percent of resources while in the background" anyway.
It doesn't matter what developer wants, it matters what customer wants.
and actually collapse their lungs when diving deep ...plus fill them with, essentially, plasma from the blood?
It has some things nicely covered - enabling really inexpensive devices, squeezing a lot from what little resources they might have; or power management. And should get more pleasant with the shift to Qt.
"Symbian will still be used in low-end devices from Nokia, Samsung, and Sony Ericsson."
plus it's not going into low-end (that is the space of S30 and, more and more, S40), it takes over middle-range (which was coming for a few years; and is now very clear with devices like, say, Nokia 5230 - touchscreen smartphone with fully free (offline) turn-by-turn navigation for less than $150 without contract as of now; and it's not even the cheapest one)
Plus it might be really not such a big deal. After all, both MeeGo and Symbian are moving towards UI based on Qt, and using it as their main API for apps.
"Heavyweight" MeeGo backend will drive their "mobile computing" devices, while traditionally more lightweight (but also more limited / moving forward more intermittently) Symbian will be on on the mainstream bulk of affordable devices, still offering something pretty close.
It's what they are doing already. S40 still lives (actually, is the largest part of what Nokia sells, and the most popular mobile phone platform), still has a future. Even S30 ships quite a few units. The plan seemed to be from the beginning to have, top to bottom, MeeGo - Symbian - S40 - S30 lineup. In time, the price range of each category moves down.
Would it really be an issue? If whole things is suspended / doesn't need anything else - no problem. If it gets max few percent of CPU, after confirming it's not even very resource hungry in first place while it just sits there and does its job - also no problem. Plus hey, there could be always a way for users to change the default. Right now they have actually less choice.
Well... http://dev.chromium.org/chromium-os/user-experience/form-factors/tablet
That seems to be only sales in given month, not "marketshare" (no way there would be 20% swings on a monthly basis); highly deceiving.
And hardware is never a money sink for Nintendo, even right after launch.
IIRC, it's more about their blood.
Lifespan of iPhone is already artificially limited. With the current prices of flash, how small part of it mobile OSes actually need, and how large part of this storage is almost always static anyway, there shouldn't be much of a problem when FS is aware of the issue and rotates the space used as swap every now and then.
Symbian devices support virtual memory for some time now, and there was no wave of them suddenly starting to die.
Lenovo has such product recently.
They do happen "automagically" in real life. Take some old app made for Win3.11, run it on latest Win version which supports it (XP?) and voila! The app can nicely behave in a multitasking environment, no changes required.
It's just the way Apple chose to implement it exclusively. But there could also be, say, a scheduler giving very little amount of resources to some old apps, when they are in the background; with majority of old apps simply having their processes suspended.
Wouldn't really require any code changes, just a setting carried over from the Appstore while updating to latest OS version / setting "suspend" by default / allowing for low resource usage while in the background after request by dev and confirmation by Apple that the app is something for which it makes sense (games? No... IM? Hell yeah!) and the app itself behaves nicely.
"Being released" is quite ok, too.
Hundreds or thousands of "gibberish" SMS, in series, will avoid attracting attention?