Live data from Hacker News

Why the iPad and the iPhone don't support multitasking

blog.rlove.org

11–20 of 65 posts

Re: Why the iPad and the iPhone don't support multitasking

#11

> "Both the iPad and iPhone, as mobile devices, have limited memory (256MB in the current incarnations) and no hard drive. No hard drive means no swap file." He loses me here. My iPhone has a 32GB SSD hard drive. Sounds like a perfect medium for swap space to me...

would anyone care to predict what the memory specs of an iphone-like will be in 5 years?

Re: Why the iPad and the iPhone don't support multitasking

#12
I would be more than happy with no multitasking at all with one exception: sms.

And I'm pretty sure that if I include another two apps (safari and mail) on my exception list most people would be okay without multitasking.

I don't need a window manager, I need to focus on the app I'm using and the ability to reply (or send) sms and mails and check something on the web without quitting the current app.

Re: Why the iPad and the iPhone don't support multitasking

#13
post #9
post #6

This guy is just wrong: Apple OS has turned off multitasking for 3rd party apps to maintain battery life. It fully supports it. This is a control situation, where Apple has decided "We want our devices to have good battery life more than we want to allow multitasking".

Best thing about those excuses are: Every other mobile OS supports multitasking and all the smartphones i know have similar battery life. Symbian, Windows, Android, all have multitasking and yet people try to convince me that it, "not needed", "not possible", "makes the device unstable", "drains battery too much" which is just not true. My Android phone lasts at least as long as an iphone and i use multitasking all t…

If I leave an app running in the background that keeps the net connection open on my Nexus One, the battery goes from 100 to 0 in about 5 hours.

Re: Why the iPad and the iPhone don't support multitasking

#15
post #3

> "Both the iPad and iPhone, as mobile devices, have limited memory (256MB in the current incarnations) and no hard drive. No hard drive means no swap file." He loses me here. My iPhone has a 32GB SSD hard drive. Sounds like a perfect medium for swap space to me...

Yeah, that's poor wording. The techie in me was aghast at the idea of Apple shipping iPhones with a full Unixy kernel but with no swap (and minimal background processing -- and for that matter, I wondered why its Objective-C runtime didn't support garbage collection) until I actually laid hands on one and realized how fluid things can be when they don't stutter and stop randomly while swapping in parts of the foregro…

"In the physical world, you never flick a real switch on a panel and then it actually moves a second or two later!"

I know some old lights which do that.

Re: Why the iPad and the iPhone don't support multitasking

#16
Saving the state of an application and terminating it isn't multitasking... you can already do that on the iPhone, and indeed well written iPhone apps will be restored to exactly the state you left them.

I care about multitasking for things which actually need to do stuff in the background, like Pandora or IM clients.

Re: Why the iPad and the iPhone don't support multitasking

#17
post #13
post #9

Earlier quoted context omitted.

Best thing about those excuses are: Every other mobile OS supports multitasking and all the smartphones i know have similar battery life. Symbian, Windows, Android, all have multitasking and yet people try to convince me that it, "not needed", "not possible", "makes the device unstable", "drains battery too much" which is just not true. My Android phone lasts at least as long as an iphone and i use multitasking all t…

If I leave an app running in the background that keeps the net connection open on my Nexus One, the battery goes from 100 to 0 in about 5 hours.

I'd bet that app was poorly written and doing something else in the background. An app that is just listening for data from an open connection should be using roughly zero CPU. But we'll try science; I've signed into AIM on my Nexus One and left it running in the background. The battery is at 81% now, I'll report back in an hour.

Re: Why the iPad and the iPhone don't support multitasking

#18

> "Both the iPad and iPhone, as mobile devices, have limited memory (256MB in the current incarnations) and no hard drive. No hard drive means no swap file." He loses me here. My iPhone has a 32GB SSD hard drive. Sounds like a perfect medium for swap space to me...

Obviously you've never used an Amiga.

No swap file + no virtual memory + lots of stuff pre-cached onto RAM disk = snappiest user experience ever.

Re: Why the iPad and the iPhone don't support multitasking

#19
post #13
post #9

Earlier quoted context omitted.

Best thing about those excuses are: Every other mobile OS supports multitasking and all the smartphones i know have similar battery life. Symbian, Windows, Android, all have multitasking and yet people try to convince me that it, "not needed", "not possible", "makes the device unstable", "drains battery too much" which is just not true. My Android phone lasts at least as long as an iphone and i use multitasking all t…

If I leave an app running in the background that keeps the net connection open on my Nexus One, the battery goes from 100 to 0 in about 5 hours.

Well, i have atleast running: Facebook, twitter, rss aggregation, gmail and k-9mail imap idle, gtalk plus weather and my phone is at around 30% end of a normal day with a few calls and around 2hrs rss reading on my way to/from work. Only one day battery life is quite sad compared to featurephones but i'd say it's normal for the smartphone of today. Oh, and i have gps/wifi turned on that day. Android 2.1 admittedly has some big improvements around that, as on my G1 wifi/gps made a much bigger difference. According to the battery stats the display is draining by far the most power anyway.

Re: Why the iPad and the iPhone don't support multitasking

#20
post #13

Earlier quoted context omitted.

If I leave an app running in the background that keeps the net connection open on my Nexus One, the battery goes from 100 to 0 in about 5 hours.

I'd bet that app was poorly written and doing something else in the background. An app that is just listening for data from an open connection should be using roughly zero CPU. But we'll try science; I've signed into AIM on my Nexus One and left it running in the background. The battery is at 81% now, I'll report back in an hour.

If you keep a connection open it drains battery life because the chip can't power down.
Post reply on HN