5 ms·
The multitasking is nice for people like me who complained, though I wonder how everyone who was defending the lack of multitasking as a good thing will take it
by jasonlotito 17y ago
The multitasking is nice for people like me who complained, though I wonder how everyone who was defending the lack of multitasking as a good thing will take it that the iPhone/iPad is now losing this 'feature.'
- colinplamondon 17y agoThe problem with multitasking is that all the prior implementations on phones sucked- it's a miserable experience on Android. This actually looks like a good solution.
- steverb 17y agoAnd that's how people will defend it.
- Terretta 17y agoSo far, the live blogging is sounding as though certain types of things will use Apple code to run those types of things in the background (eg., audio streaming, answering events, etc.). Hopefully this isn't going to allow apps to just run any random equivalent of a tight loop of their own (memory chewing CPU and battery consuming) design. I'd also like a reverse chronology notification history that pops up from tapping on the click.
- enjo 17y agoWhich limits an entire class of applications. It's not multi-tasking, it's system services that multi-task for you. To even call it multi-tasking is a joke.
- metachor 17y agoWhat is a use case for multi-tasking on a phone that you want/need that could only be covered by full preemptive multi-tasking of third party apps?
- mortenjorck 17y agoSETI@iPhone.
- locopati 17y agoMultitasking on the Pre works pretty darn well
- nailer 17y agoYeah, having used iPhone and Android for a while, the Pre's implementation blows them both away.
- jasonlotito 17y agoWhich has nothing to do with what I said. I was referring to the people defending the lack of multitasking as a feature. They would always crop up. Indeed, I remember one person using that same argument: That other MT implementations sucked, Apple shouldn't/couldn't do it for the iPhone. The reality is, MT was a missing feature, and it took them till revision 4 to deliver it. It wasn't because MT isn't important. It's because they didn't know how to implement it. That's a fair reason. I didn't see people suggesting that, and they were right.
- Batsu 17y agoI've had no qualms about multitasking on my Hero. Switching between my browser and gchat is a matter of holding down the home key for 3 seconds and pressing on whichever icon I want to go to. Things that run in the background, such as uploads, leave a notification on the top when it's finished. What's so bad about that?
- colinplamondon 17y agoThe management side- I have to have a Task Killer app running in the background to kill off all the random apps that wind up going. The problem on Android, to me, is more of a failure in caring about UI than a failure of technology- which is also my problem with the platform as a whole.
- orangecat 17y agoI have to have a Task Killer app running in the background to kill off all the random apps that wind up going No, you don't. Just because an app shows up in a process list doesn't mean it's consuming resources. (Other than memory, and background processes are automatically killed as needed to free up RAM).
- nooneelse 17y agohttp://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-with-android/ http://geekfor.me/faq/you-shouldnt-be-using-a-task-killer-wi...
- jpcx01 17y agoSeriously? Have you used a droid or a nexus one? Multitasking has been one of the killer features for me. Swap between the web browser, email, podcasting app and it never loses your spot. There's no going back once you really feel like you have a computer in your pocket. Really hoping iPhone 4 can replicate this experience.
- gamble 17y agoAbsolutely. There's a reason that task manager apps are popular downloads for every phone that offers multitasking. You won't see them on iPhone OS 4.0.
- rimantas 17y agohttp://www.engadget.com/2010/04/08/jobs-if-you-see-a-stylus-or-a-task-manager-they-blew-it/ http://www.engadget.com/2010/04/08/jobs-if-you-see-a-stylus-...
- orangecat 17y agoThere's a reason that task manager apps are popular downloads for every phone that offers multitasking. The reason is that intermediate users who know just enough to be dangerous think that they're necessary, when they aren't: http://droidtalk.net/should-i-install-a-task-managerkiller-on-my-android-device/ http://droidtalk.net/should-i-install-a-task-managerkiller-o...
- gamble 17y agoAndroid gives app developers enough rope to hang themselves, or at least waste the battery by constantly firing up the radio or GPS. I agree that you don't need a task manager to conserve memory, but there's no automatic solution for overactive apps except the automatic cleanup for long-running apps. Even the link you supplied admits it: "Is it really necessary to be notified about every new tweet or status update? Reduce the refresh times on your social networking applications and reduce the number of items you’re notified about. Reduce the number of widgets you have on your home-screen, instead replace them with program shortcuts, you’ll still have quick access to your most used programs without the constant battery drain caused by continuous data pull."
- rimantas 17y agoThere is "defending" and there is "understanding the limitations". Apple found a way around those limitations: to offer seven background services which iPhone can offer to your Apps. That kind of gives you multitasking and still leaves resources control to Apple's code in iPhone OS. Update — services offered: Background audio VOIP Background location Push notifications Local notifications (don't require the server) Task completion (e.g. Flickr's upload can continue in the background) Fast app switching (storing/restoring app's state)
- jasonlotito 17y ago"There is "defending" and there is "understanding the limitations"." I agree. I'm referring to the defenders. The people that were actively pointing to reasons why multitasking for the iPhone/iPad were bad for non-technical reasons (screen size, the UI, they didn't need it, etc.) There were lots. Every time multitasking was brought up, they would offer countless reasons why multitasking was bad. Which was all just a cheap way to defend it's lack of multitasking. Multitasking was never a bad idea. It was always a missing feature. Regardless of the reasons for it, it's clear that they've finally overcome the problems. Their inability to do so until now shouldn't have shielded them from criticism early on.
- tptacek 17y agoStrong disagree. Apple's implementation of background services looks more like a vindication of the defenders. They didn't simply get their act together and make apps run in the background; they set the bar significantly higher than that.
- jasonlotito 17y ago"Strong disagree. Apple's implementation of background services looks more like a vindication of the defenders." But it's not. And you can disagree, but you are wrong. The defenders I'm referring to were supporting not having multitasking; or, better said, were touting lack of multitasking as a feature. Their were other defenders who were for multitasking, but against doing it poorly. I'm referring to the former, not the later.
- gte910h 17y agoOh I still hope it's a per-app settable option like notifications are. It was never a feature, it was a choice to prolong battery life. We'll see if the other side of the tradeoff is worse or better on the whole once it is put in everyone's devices.
- DannoHung 17y agoWell, personally, I'm not convinced that the implementation is good yet. They haven't addressed how they've avoided battery life implications OR how to actually quit an app yet, so you've still got the potential of the Android multitasking problem in that the UI is unintuitive. Also, I already have double-home button mapped to bring up the iPod controls and go to search. I don't like that that'll be going away. Though I'm not surprised that the implementation they're going with is allowing apps to have smaller background services instead of full on multitasking. I'm gonna let them finish before saying whether it's the best multitasking phone of all time though.
- tvon 17y agoJobs was very specific in saying that they managed to add multitasking without sacrificing battery life or performance. I suspect that's where people would point. edit: That is if you believe the real reason was for performance. Personally I think it was half that, and half that they hadn't come up with a good way to present it to the user. edit 2: I think this sums it up exactly: "(...) in multitasking, if you see a task manager, they blew it" - Jobs in Q&A.