Linked by Thom Holwerda on Tue 17th Mar 2009 18:43 UTC
Apple Apple held an event today announcing some of the new features coming in iPhone OS v3. Thee were loads and loads of new features, but the big ones are cut/copy/paste functionality, push notifications (I guess most developers will believe it when they finally see it), spotlight search, and many others.
Thread beginning with comment 353478
To read all comments associated with this story, please click here.
Comment by BSDfan
by BSDfan on Tue 17th Mar 2009 20:19 UTC
Member since:

I don't own an iphone, but can someone explain why it can't "multitask"?

The phone is based on BSD/Mach, why would Apple seriously prohibit multitasking artificially?

Reply Score: 1

RE: Comment by BSDfan
by apoclypse on Tue 17th Mar 2009 20:22 in reply to "Comment by BSDfan"
apoclypse Member since:

Battery life. That much should be obvious. That's pretty much what they have said since the iphone came out.

Reply Parent Score: 1

RE[2]: Comment by BSDfan
by flanque on Tue 17th Mar 2009 20:31 in reply to "RE: Comment by BSDfan"
flanque Member since:

Not exactly sure it's obvious.. my Nokia can run multiple apps at the same time.

Reply Parent Score: 6

RE: Comment by BSDfan
by JonathanBThompson on Wed 18th Mar 2009 02:32 in reply to "Comment by BSDfan"
JonathanBThompson Member since:

Here are the facts:

1. The iPhone absolutely does multitask, in more ways than one: this leads to #2:

2. The way that it multitasks (using the loose definition being bandied about in here) is with the built-in Apple provided applications combined with whatever 3rd party apps are running visibly in the foreground, but this isn't the only way it actually truly multitasks:

3. Developers *CAN* write multithreaded applications that run just fine, without a problem: if they don't do that, don't look at Apple, because Apple didn't tell them they couldn't.

The price for all the power OS X and the frameworks is that it all takes a lot of RAM, unfortunately, and this makes things surprisingly tight, it seems. Personally, I'm hoping for the next major revision of the hardware to at least double the non-FLASH RAM, as doubling the actual non-FLASH RAM would more than double available application RAM, due to OS and video buffer management overhead.

Reply Parent Score: 2

RE: Comment by BSDfan
by ari-free on Wed 18th Mar 2009 06:09 in reply to "Comment by BSDfan"
ari-free Member since:

you need an appropriate UI to handle the multitasking, not just the kernel and Apple didn't think of one for that form factor.

Reply Parent Score: 2

RE[2]: Comment by BSDfan
by JonathanBThompson on Wed 18th Mar 2009 08:39 in reply to "RE: Comment by BSDfan"
JonathanBThompson Member since:

What makes you think that the GUI they use is not the appropriate GUI for multitasking, or, for that matter, exactly as much multitasking as they intend to be exposed?

Do you have development experience on the iPhone OS to indicate that the GUI itself is incapable of multithreading/multiprocessing and dealing with that correctly?

It's important to remember this: the iPhone was (and still is) a product of engineering, and engineering is the budgeting of reality, and one of the biggest budgeting issues that's very important for mobile devices is that of battery use, and that has to be balanced with providing the overall GUI and other design goals, which also happen to include an OS with a rather rich GUI and other rather large, memory-consuming libraries to build things from. Also, the general main purpose of the iPhone is... to be a phone with a very usable and flexible graphical interface that also isn't too complex to use for non-geeks. Is it perfect? But ask yourself this: is any GUI for a portable device capable of being called perfect? Given the multitouch, the pure graphics display for the interface, I think Apple's design decisions (for the most part) are a coherent holistic design, when you consider their target market: they weren't aiming for the technogeeks that get all sticky over having all the gadgets and specs possible, which tends to end up with a kitchen sink mentality with a cluttered interface, but rather something that is rather intuitive for even the most computer un-savvy to readily pick up and use quickly. Ok, they didn't even get that perfect in my judgment, either... but trying to cram a full Windows GUI from a desktop onto a smaller graphical screen, and forcing people to do things like use a stylus, that doesn't exactly come off as friendly or 100% obvious, either ;)

Reply Parent Score: 2