4 ms·

Can someone please explain to me why this was modded down? I'm curious, as I am unaware of the Apple multitasking history. (Had an 8086, and an Apple II at sc

by jbm 16y ago

Can someone please explain to me why this was modded down? I'm curious, as I am unaware of the Apple multitasking history. (Had an 8086, and an Apple II at school; never encountered apple again until after I got an iPod and then an iPhone)

ugh 16y ago
Recently someone compared weird downvotes to cosmic rays. They are going to strike but they are mostly harmless. Upvote back and carry on. On topic: I’m not sure whether architectural decisions hamper iOS multitasking – it seems to me that the UI for multitasking in iOS just isn’t very good [0]. There are some edge cases where true multitasking would be great but I think that Apple is for the most part facing an UI problem, not an architectural problem. [0] There isn’t much of a multitasking UI, actually. There is this horribly inaccessible row of recently accessed app icons and nothing else. If only it weren’t beneath Apple to shamelessly copy WebOS or Android.
- loire280 16y ago
  I suspect most people never noticed the addition of multitasking in iOS. Suddenly Pandora didn't stop playing when they checked a mail message and their apps reopened much faster, but they probably credited/blamed the app developers for that. I wonder what percentage of users don't even know about the double-click-home menu. I think multitasking UIs on touch devices (where apps are usually 100% of the screen) are more confusing for users than just going back to the icon on the home screen. Users get that more than one thing is running at a time in a windowed environment -- you can see both of them at the same time if you position your windows properly. I'm not sure they bring that understanding along when they pick up a tablet.
  - bane 16y ago
    I don't totally disagree but multitasking doesn't have to be only user-facing apps. The notification system in Android is light-years ahead of iOS and it relies entirely on having a good multi-tasking environment. Importantly, the notifications don't have to just be from some specific set of things-that-can-notify a user as chosen by Google. Pretty much any kind of app can notify a user of anything. In theory iOS is more than capable of supporting this on the backend, but the front end architecture is a mess and would have to be significantly reworked for even this kind of basic thing (well, it seems basic on an Android device it seems so obvious there).
    - loire280 16y ago
      My main problem with multitasking on iOS is that there isn't a good startup service implementation -- so for example if I restart my phone and don't open Google Voice at least once, I won't get push messages from it. However, one of the reasons the platform performs well (esp. with battery life) is that the OS can kill a background process at will, and apps expect that and are usually designed to handle that gracefully. Hopefully there's more work coming to make this less of a trade off, especially as new phone versions have more resources.
kenjackson 16y ago
The Mac had cooperative multitasking until I believe Mac OSX. They were nearly the last OS to get preemptive multitasking by a factor of like 5-6 years. The Mac was technologically out front when it came out and then for 15 years just seemed to stand still. Architectural elements like multitasking and memory management just became dated while systems like Windows made the Mac OS look archaic. Until OS X. I think the other commenter is alluding to iOS maybe following the same trend, but this time to Android.
- bane 16y ago
  Yeah, that's exactly what I was thinking about. History tends to repeat itself. The shift from cooperative multitasking to preemptive was an extremely painful experience for Apple. How many failed OS projects did they have before they just threw in the towel and bought NeXT? I hope that the modern equivalent doesn't go the same way for their mobile solution.

by jbm 16y ago

ugh 16y ago

Recently someone compared weird downvotes to cosmic rays. They are going to strike but they are mostly harmless. Upvote back and carry on. On topic: I’m not sure whether architectural decisions hamper iOS multitasking – it seems to me that the UI for multitasking in iOS just isn’t very good [0]. There are some edge cases where true multitasking would be great but I think that Apple is for the most part facing an UI problem, not an architectural problem. [0] There isn’t much of a multitasking UI, actually. There is this horribly inaccessible row of recently accessed app icons and nothing else. If only it weren’t beneath Apple to shamelessly copy WebOS or Android.

loire280 16y ago
I suspect most people never noticed the addition of multitasking in iOS. Suddenly Pandora didn't stop playing when they checked a mail message and their apps reopened much faster, but they probably credited/blamed the app developers for that. I wonder what percentage of users don't even know about the double-click-home menu. I think multitasking UIs on touch devices (where apps are usually 100% of the screen) are more confusing for users than just going back to the icon on the home screen. Users get that more than one thing is running at a time in a windowed environment -- you can see both of them at the same time if you position your windows properly. I'm not sure they bring that understanding along when they pick up a tablet.
- bane 16y ago
  I don't totally disagree but multitasking doesn't have to be only user-facing apps. The notification system in Android is light-years ahead of iOS and it relies entirely on having a good multi-tasking environment. Importantly, the notifications don't have to just be from some specific set of things-that-can-notify a user as chosen by Google. Pretty much any kind of app can notify a user of anything. In theory iOS is more than capable of supporting this on the backend, but the front end architecture is a mess and would have to be significantly reworked for even this kind of basic thing (well, it seems basic on an Android device it seems so obvious there).
  - loire280 16y ago
    My main problem with multitasking on iOS is that there isn't a good startup service implementation -- so for example if I restart my phone and don't open Google Voice at least once, I won't get push messages from it. However, one of the reasons the platform performs well (esp. with battery life) is that the OS can kill a background process at will, and apps expect that and are usually designed to handle that gracefully. Hopefully there's more work coming to make this less of a trade off, especially as new phone versions have more resources.

kenjackson 16y ago

The Mac had cooperative multitasking until I believe Mac OSX. They were nearly the last OS to get preemptive multitasking by a factor of like 5-6 years. The Mac was technologically out front when it came out and then for 15 years just seemed to stand still. Architectural elements like multitasking and memory management just became dated while systems like Windows made the Mac OS look archaic. Until OS X. I think the other commenter is alluding to iOS maybe following the same trend, but this time to Android.

bane 16y ago
Yeah, that's exactly what I was thinking about. History tends to repeat itself. The shift from cooperative multitasking to preemptive was an extremely painful experience for Apple. How many failed OS projects did they have before they just threw in the towel and bought NeXT? I hope that the modern equivalent doesn't go the same way for their mobile solution.