Multitasking In For iPhone 4.0?
The latest word on the iPhone is that the 4.0 OS will finally have
honest-to-goodness multitasking. This could hopefully lead to things like a real chat client, and dangerous battery consumption. I still hope it's true.
this would be AWESOME for the ipad, might even make it worthwhile.
People, what a bunch of bastards
I think i've heard this before...
If you can really use iPhone for more than 3 hours for an heavy user, magine with multitasking....
These kind of apps make me laugh. You've got a phone with SMS & web browsing capabilities, and you want a chat client?
It's a computer with wireless.
Deleted
Yep, it should perform only one task at a time, ie either transmit what_you_speak or receive what the other person speaks. Just like a walky-talky. Sound absurd? So is your argument!
YEAH! Why have a cell phone.. I think there are pay phone things somewhere... I saw one on Superman.
~Mekkah
What if I want to use a streaming music player and some other app at the same time? As it stands, current iPhone OS is capable of multitasking the built-in iPod software with other apps, but not streaming music with other apps.
The iPhone OS has always had real pre-emptive multitasking. The phone, email, iPod, calendar, and other applications run all the time and can do things simultaneously.
Multitasking just hasn't ever been made available to 3rd party developers.
It has never been a technical limitation in the OS. Rather, Apple kept control over it for battery life and security reasons.
First against the wall when the revolution comes
There are real uses for multitasking, which the iPhone already does - like listening to iPod while surfing or the like. Maybe chat as mentioned, but I also hope to set which apps can be multitasking - I don't trust the developers always to make the correct call - there is no reason to leave a game running in the background while I surf, it would be better to save state. I would actually say saving state and resuming again is better the vast majority of times over running in the background.
But oftentimes I try to hang up the phone by hitting the home button instead of the end call button (even though I think I did), and while surfing, I still see that "Return to Call" blinking on top.
To conserve battery life, I already turned off push notifications and other things. And I would turn off multitasking for my parents phones, they hardly can use a computer as it. With this, they'll only be wondering why the phone battery is dying even faster.
If I wanted a freakin' phone I would have just bought a RAZR or something, but I wanted a SMART phone. You don't think iPhone users want this? *raises hand* I do!
This is why Apple should sue the shit out of Google, because once iPhone OS 4 is available, Google will inevitably steal every single idea from it.
Except it's not just a phone ... it's a "smart phone."
The term may be vague/undefined, but it's understandable that some think it implies a more general computing environment. Apple's "app" concept doesn't help that perception. Why should multitasking be such a foreign concept?
You've got a phone with SMS & web browsing capabilities, and you want a chat client?
As I understand it, you can't SMS to or from a U.S. land line. Nor can you SMS to someone who primarily uses AIM, Windows Live Messenger, EFnet IRC, or Freenode IRC.
At one point when looking into developing an Application for the iphone, one of the requirements for *all* apps is that it had to be able to close with in a small time window upon hitting the home button as to kill any chance of running more than 1 app at a time. The reason for this, as I read it, was to avoid having a ton of applications running (w/o the user aware) and killing battery time and other software conflicts. I'm not really sure thats a bad thing. I can remember with my blackberry, If I got a call while in an application I may forget and before I knew it--dead battery. Since it's a phone first and a app platform 2nd, multitasking might not be the best thing for it.
i was gonna ask what's the point of chat? but i suppose if it could more than 2 people at a time, that could be useful.
"To stop the terrorists."
not having multi-tasking means you cant run the chat app in the background, so everytime you want to go to your webbrowser, the chat app completely closes, you go offline etc...
so even when not chatting with multiple people at the same time, this could be extremely usefull for chat apps
People, what a bunch of bastards
Well if full-duplex is your definition of multitasking, you'll be pleasantly surprised to know that the iPhone already multitasks just as well as the StarTac.
https://www.eff.org/https-everywhere
But if they do allow multitasking, I hope Apple becomes MORE restrictive on what they let on the App store. I don't want crap apps sucking my battery down.
As a developer concerned with power usage I would like more access to tell the OS things like how often I need a GPS location update. You can tell the API to update your app when you have moved x distance, but that implies the OS is watching movement constantly and only updates you every so often. I'd also like to shut down such resources when on a screen that doesn't need them, if I can quickly bring them back up.
Think Deeply.
So people that use the iphone never want to say use last.fm or ustream and aim or some game at the same time? Just from a user prospective I would like to be able to use more then one app, that is not part of the default install.
This is why I jailbroke the thing in the first place (well, that, and a few other things): multitasking for everything, not just Apple's apps. For some time now, I have been able to listen to music and browse the web, text, chat, etc. by just switching apps. It works fairly decently, too, and doesn't make it very slow. I am simply amazed they decided this was a proper limitation.
SSC
I guess we should thank god that our overlords at Apple didn't release the first version of iPhone with a DOS/BASIC prompt!
Multitasking comes now -- what's next? Multiple windows?? Hallelujah!!
And it'll be on Verizon's network, too.
Best Slashdot Co
Obviously, they do want it. And I was in the "geez, why doesn't Apple enable true multi-tasking?" crowd along with most other people. However, after playing with my new iPod touch (thanks sis - she knows I'm too cheap to buy this stuff myself) and comparing it to my Android, I think Apple is smart.
The Apple UI is so smooth compared to Android's, there really is no comparison. I HATE lag when I'm dealing with a UI, and Android's multi-tasking Java based applications take a good 1-3 seconds to do anything I tell them to do. If there's any chance Apple would have impacted their UI performance to enable multi-tasking, I think they made a great move.
I still wouldn't switch from an Android to an iPhone because of the restrictions (and I'm not going to wager hundreds of dollars on a jailbreak), but now I see why people enjoy Apple products.
For most users multi-tasking is a secondary concern to a nice UI.
If you can read this... 01110101 01110010 00100000 01100001 00100000 01100111 01100101 01100101 01101011
It also means AT&T will make more money as apps that use the internet will be backgrounded and sending bits of data.
What Android phone do you have? My Motorola Droid is mostly instantious (give or take a few milliseconds) unless it's low on memory. Sure it has the occasional slowdown, but 98%+ of button presses are more or less instant.
I have no problem with the Android UI. It's pretty damn simple. Press the button on what you want to do, and there is an auxillary button for options. I havn't used an Iphone, but what do they do that's really so much better?
With multitasking, how do you know that a thread doesn't get spawned off that now runs and listens on an arbitrary port for incoming connections?
That's not an argument against multitasking but an argument for using the kernel to block incoming connections to ports other than those that an application has specified in the manifest.
A real chat client? What's missing from it currently? BeeJive with push notifications enabled has been as good for me as any backgrounded chat app I've ever used.
In the old days, we had background processes that always had to run. Now we have signals and the like that can awake idle processes so they do not have to run. Then we had TSR applications, and similar items on the Mac, like the Talking Moose. The former was created to solve the long start up time of applications on DOS and Windows. Multiple windows and such were useful on the PC, with larger screens, but somewhat harder to use on the Mac. The Mac seemed to launch applications faster, so I don't have a recollections of being annoyed that Finder was not multitasking.
Multitasking is a solution to solve some problem on the general computer. I am not sure it is the right solution for a small screen mobile small battery device. I would rather see innovative solutions rather than rehashing the same old thing. I think there this might be a useful solution for the iPad. My concern is that iPhone 4.0 is built for the next iPhone, and will make current iPhones harder to use. This is what happened with iPhone 3.0, which does not run very well on the first generation iPhone.
"She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
The Nokia N900 has multitasking and is fully open
Which U.S. mobile phone operator carries the Nokia N900? Or if you happen to live in a T-Mobile covered area, which U.S. retail store chain carries an unbranded Nokia N900 that I can try before I buy?
Android Lag? Check out a Nexus One. I had an iPhone user today try mine out and literally order one 10 minutes later. Thanks Snapdragon!
The big issue for me is battery life. I don't want some random app draining the battery of the device I use to call a tow if my car breaks down.
Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
iPhone2G is as powerful as iPhone3G, but Apple seems now to forget these old models. New firmwares for 2G lack features found on 3G. I hope FW4 won't be for "3G / 3GS / 4G only". First iPhone buyers love Apple; Apple, love them !
-- Rastignac was here.
Yes.
What android phone are you using? I have a nexus one and it is just as snappy as any Iphone, at a considerably higher resolution. There are also optimization techniques that Google hasn't made prime-time yet, that really increase the overall performance of all apps running in a dalvik vm: zipalign-on-install.
Apple's decision to not include multitasking from the start was likely a decision to keep things as simple as possible. Now they're playing catch-up and tacking on multi-tasking to a system that was built from the ground-up without it. I don't understand how this will not break app compatibility. Existing apps only understand certain "states." Multitasking will introduce new application states that existing apps will not know how to handle. I am very interested in how they plan to reconcile this.
Similes are like metaphors
... that Apple will open up the app store, and will allow any and all third party applications. In addition, multiple sources indicate that the iPhone 4.0 will cook dinner and fold the laundry.
In other news, multiple sources are rumors, same as always.
Can't wait to see the next Hitler Responds to... video about this.
As a counter to your example, I tried a Nexus One a couple weeks ago and still prefer my iPhone 3G. Just putting it out there.
I just don't get... eh, ugh... never mind. This post wasn't worth the research I put into it.
Anytime you mention multitasking to an Apple fanboi they come up with 20 reasons why it's a bad idea and wasn't implemented. I'm sure they're just irate about this new feature and will be pissed off to no end that Apple is adding it, right?
I've got the first t-mobile phone; I bought it a year or so ago, so the hardware is a bit slower. But I find that when I've got browsers going, along with my background weather program and I fire up a map or a game, things are extremely slow. Yes, I could go in and close everything down, but with Apple I hop from one task to the next. However, even if I did close everything down, the UI wouldn't be as responsive (again, maybe it's the hardware or the multiple Android OS patches that have been sent my way or the last few months)
Smooth, simple, easy. And speaking for myself, when I'm using a portable computer, that's all I really need. But that's just MHO
If you can read this... 01110101 01110010 00100000 01100001 00100000 01100111 01100101 01100101 01101011
With multitasking and iWorks, I can actually get something done with it while pissing away my life on the subway or on a bus. Now all I need is for Adobe to come up with PDF support on the iPad, and I am one happy camper.
RS
Shoes for Industry. Shoes for the Dead.
I've had my Nokia N900 for a couple of months now, and for those unaware, most of the specs are identical to the iPhone 3Gs 32Gb. Well, except that it has a much higher resolution screen, a keyboard, a real GPS, an FM transmitter and a microUSB port for data and charging. But the CPU/GPU and amount of storage are the same, except that you can also add a microSD card to the N900. But now on to the most important difference to the 3Gs. I've used both my N900 and a 3Gs, and the 3Gs just feels sluggish, while having half the functionality.
Flipping home screens on the N900, regardless of how many icons and widgets it's running is smooth, with no clipping. Even with half a dozen apps running in the background, the UI remains equally fast (several instances of the Firefox, Application Manager, Communication app, Contacts app, Skype, MediaBox, battery-eye, conky, etc). Flipping through the 3Gs icon screens clips and feels choppier. It's not a large difference, but keep in mind the hardware is identical and the iPhone has NO applications running in the background.
The N900 also starts up applications faster, in most cases instantaneously. Start up times do increase progressively after about 3-4 large apps are already loaded and actually doing stuff in the background (Firefox loading up pages, Application Manager checking for updates, MediaBox playing music). But many utilities that only refresh while in the foreground do not have any impact at all (Conky, battery-eye, disk usage, etc). In contrast, the 3Gs takes a couple of seconds to load up pretty much every app I tried, regardless of how limited its functionality is, and complex apps take even longer.
Once the apps are running, they are roughly equally fast on both the N900 and the 3Gs. But as I stated above, the N900 may be running several apps in the background, and the foreground apps do not slow down at all.
I think this is why Apple did not allow multitasking up to now. Given how slowly single apps load on their flagship 3Gs, true multitasking will bring it down to its knees. The iPhone OS takes much more resources to run than Maemo or Android, and the iPhone single tasking is a way of masking it. Of course this is speculation since except for the basic Apple apps, nobody managed run more than one app at the same time on the iPhone. And I'm sure those Apple apps are optimized and tweaked to hook into the OS and stay loaded at all times. Most likely the 4G will have a faster processor and more RAM, and will compensate for the OS shortcomings through brute force.
It can, but Apple won't let you becasue they don't see the need for you to use the device how you want. It is all about what Apple wants.
"I still wouldn't switch from an Android to an iPhone because of the restrictions (and I'm not going to wager hundreds of dollars on a jailbreak), but now I see why people enjoy Apple products."
The current Jailbreaking method is actually very ease to implement and just as easy to undue.
Pretty much you download an EXE from blackra1n.com and then run it. Boom Jailbroken.
To undo the Jailbreak simple do a factory restore on phone from itunes.
There are more complex ways to do this, but the above method is pretty safe and simple. //cool story bro...
I could do this ages ago with jailbreaking (Backgrounder, Kirikae, etc). But I do wish that in Android it would make backgrounding not default unless I set the program specifically to background.
Apple, Welcome to 2005 and the Nokia N770 http://en.wikipedia.org/wiki/Nokia_770_Internet_Tablet. Way to go!
OTOH, I suppose you sold more iPhones **today** than all the 770s sold since they were released.
Disclosure: I have a $200 (new) Nokia N800 and routinely multitask email, music, podcost downloads and browsing while at home.
When on the driving I multitask GPS (maemo-mapper) and music/podcast playback.
When hiking, I run Maemo-mapper and GPSView to help find those geocaches.
The GPS stuff helps me to geotag my photos later. Scroogle "N800, photos, gps" for more information.
Best of all, no cell phone contract.
Someone asked about the best way to get a Nokia N900 in the USA. If best is cheapest over a 2yr life, then buy it unlocked from amazon and bring your GSM SIM card with you to the N900.
Again - Apple - welcome to the show. You should be commended on your innovative efforts!
Really? I've had quite the opposite experience with my Droid. Lots of freezing/crashing, and lots of instances of programs continuing to run in the background when I want them closed draining my battery and heating up my phone. If I didn't loath AT&T so much I'd go back to the iPhone in a heartbeat, multitasking or no. As it is, I'm hoping the 2.1 patch (if it ever gets here) at least irons out a few of the kinks.
I don't think it would be that difficult from a third party app's point of view. The background app's state could still be "off", just like it is now. Then app makers could release a new version that supports multitasking in a background state if they feel their app could make some use of this.
www.clarke.ca
Beejive seems to handle messages well enough with push notifications if you have to switch out to another app for a bit and most modern (hell even ICQ) chat services can handle offline messages. It can also do multiple chat sessions/services at the same time so you don't need multitasking to do that.
The screen is rather small as it is for just doing one thing at a time so if I'm not in the chat app I don't won't chat windows taking up all or some of the window when I'm doing something else.
Are these some examples of ANECDOTAL EVIDENCE? My favorite!
My grandmother used anecdotal evidence all the time, and she lived to be 120 years old.
Taking a shit at work, listening to last.fm, playing Sudoku, and IM'ing friends on my phone, all at once... No way would I give that up for a slightly smoother UI.
Actually, the kind of background processing that the Newton used, which has some things in common with what Android does (specifically Android "services"), would be awesome. The main problem is that developers are really not used to working this way.
Basically, you have your main app, and it runs when it's in the foreground, and that's it. But you also have these other chunks of code that the app can register with the system. On the Newton you could attach that code to the OS-level alarm mechanism ("when this alarm that I just asked the system service to execute for me at that timestamp fires, don't show a dialog box or play a sound, run this bytecode instead"). On Android, it can be a daemon-like thing that actually runs in the background (eg. to play streaming music).
The fundamental idea is that the whole app isn't doing background processing -- instead you break of very small pieces and those run in the background, under much more severe constraints. (The distinction between cron-like and daemon-like isn't really critical here. The developer still has to be trained to break their app up into distinct pieces with different constraints, instead of having one big app.)
This is simply not the architecture a lot of developers are used to (though Unix folk have a head start). But it's a way to provide actual real usable multitasking on a device like this without crushing the memory and battery usage (especially if you use the alarm-based method and your apps can schedule the alarms far apart; for some apps this is more than adequate).
Some programmers would certainly yell if they had to jump through that kind of hoop. But something like that could very well be the best compromise on these devices.
Apple's decision to not include multitasking from the start was likely a decision to keep things as simple as possible. Now they're playing catch-up and tacking on multi-tasking to a system that was built from the ground-up without it. I don't understand how this will not break app compatibility. Existing apps only understand certain "states." Multitasking will introduce new application states that existing apps will not know how to handle. I am very interested in how they plan to reconcile this.
iPhone OS is Unix. It's had multitasking built in from day one!
I hate to be semantic here, but the iPhone uses a unix based kernel, and at its heart already does multitasking. Beneath the user facing side, many processes run simultaneously already. What most of the posters here, and TFA are referring to is the ability to run multiple user-facing apps at the same time. This feature has been disabled to simplify the user interface and to reduce battery depletion. While we can debate the merits of that decision, the assertion that the iPhone is like a mid 1980's computer because of a lack of pre-emptive multitasking is fallacious.
This and no other is the root from which a tyrant springs; when first he appears as a protector - Plato (423 to 327 BC)
How many of the current apps will need updates because the programmers forgot the simplest of lines of code... close(); ...?
Shiny. Let's be bad guys...
Palm's WebOS has had FULL multitasking for ALL apps since Summer 2009. Go check out a Pre or Pixi on Sprint or a Pre +, Pixi + on Verizon. All the "Oh look at the cool multitasking things we can do" on the latest 3Gs commercial? WebOS had it out of the box last summer.
Oh, and then there is the remarkably simple development platform (Web standards! Yay!) and the vibrant non-official apps catalog available in the free PreWare and WebOS Quick Install applications that work in perfect sync with the Official WebOS Catalog.
(Palm has actually been helping the community integrate the sideline catalog, and encouraging mods and patches to the base WebOS setup. Imagine that!)
For all the hype about Apple (and Droid) NEITHER of them can yet do what Palm has already accomplished in less than a year.
Stop dicking around with Apple slaveware and Google's multiple personality disorderware. Go get a Pre or a Pixi.
Official Heretic from the "Church of Global Warming". Proven right thanks to whistle blowers. AGW = Flat Earth Theory
Your post has made me curious and I’m watching now the review of the N900 right here: http://www.youtube.com/watch?v=PvPTBwEg5UA
Now, I dunno if my perception is screwed or something but the apps on there take 2-4 seconds to launch and the touchscreen does lag tiny little bit in some of them.
On the other hand the apps on the vilified 3gs load - as far as my perception is concerned - within 1-2 seconds.
Damn straight! Best way to spend a Thursday afternoon!
I just don't get... eh, ugh... never mind. This post wasn't worth the research I put into it.
How bout they just make it so everytime I click on soemthing I want in the app store it doesn't close the app store to "install" it. Seriously.
Hell, I have a G1 and it's fine unless I load some long webpage full of Javascript and I'm talking about something worse than Slashdot which it handles fine.
buy an unlocked version from the Nokia shop
I would, but the closest Nokia shop is 200 miles away. Where do you recommend that I try the phone before I buy it?
In the US, you would be able to use it on any GSM network, which I believe means T-Mobile or AT&T.
That's a possibility, as T-Mobile finally gives a discount for bringing your own handset.
Now there are 2 tasks. You have multitasking; steve jobs' style
hey, aren't you they guy who said they wouldn't be able to add copy/paste since it was built from the ground up without it?
Because the only app that you can use to listen to music is the iPod app
He didn't specify how he listened to music. As even you admitted, the iPod app happily plays music. Therefore, the correction was correct.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
..except for the phone and iPod app which has had multitasking since launch.
I have jailbreakon my iPhone and installed "backgrounder" which allows any app to run in the background. Works great. The icon of an app gets a small circle to indicate that it is running in the background.
I do understand why Apple have blocked this functionality to developers since it drains battery.
Sounds like Apple's ripping off Android now. Maybe HTC should sue them back.
I can't stand hearing everyone talk about multitasking on things like Android devices as though it works the same way as it does on their desktop PC. Nothing could be further from the truth.
The first form of multitasking on Android is that applications can elect to receive messages, e.g. "someone is calling", or "wifi state changed".
If you actually need to do constant work in the background (e.g., listening on a network port), you can do so as well, using a "service". And even services will be killed by the system if resources are needed.
No one is talking about running a Handbrake encode session, Firefox with a bunch of animated Flash ads, and a kernel compile at the same time on their phone.
Multitasking on a phone is being able to record breadcrumbs of a journey with a GPS app, listen to streaming internet radio, and receive notifications from an instant messaging client at the same time.
I'm a hardware guy and after swapping from Nokia to the iPhone then to a HTC Magic my next update will be a Dell Mini 5. I really like android and it's openness and now that Android has near 40k apps the iPhone app store doesn't interest me.
What's wrong with buying your music and synching it on your phone if you want to browse at the same time?
Another Slashdot user mentioned "a wealth of great music released [that] isn't on heavy rotation on radio". But people don't have the money to buy every album that comes out, and people want to try it before they buy it.
Would be extremely useful.
I can see in a car where you'd have an in-dash touchscreen (the 5" or whatever the screens are) and a "port" for your iPhone.
Once docked in the port, your iPhone display is on the in-dash display, and integrated with the stereo, the handsfree controls for phoning, etc.
That would be pretty nice.
But that is the key, YOU getting the choice, not Apple.
---- Booth was a patriot ----
I think Apple should use a bytecode execution engine and explicitly timeslice jobs. They could modify LUA or Python, providing bindings to a limited, safe set of native API calls (or safe wrappers to them).
Then, iPhone app developers would have the option of providing an explicit LUA/Python/whatever script as part of their app. The only promise Apple would make is that the script would not be guaranteed to run quickly.
The scheduling could be something simple like this:
- Give each script its own small heap, stack, and VM state
- For each script, execute its bytecode for up to 20 milliseconds (or some dynamic value based on load)
- After all scripts have executed their timeslice, sleep for 1 second.
- Start again
Having a ton of background processes from a ton of different apps could cause starvation, but that would happen in a much worse way with unconstrained multitasking.
Apple doesn't bend over backwards to preserve compatibility. They're just going to drop your app from the store if it doesn't work after upgrading the OS; hasn't that happened already?
Some use cases off the top of my head:
- Let me know when I've come into the vicinity of a historical landmark
- Synchronize my media from the cloud onto my device in the background (over, say, 3G)
- To always feel rich by knowing that I Am Rich is still running in the background.
The Unix process model doesn't work like you think it does. I'm not sure how you got modded as Insightful on this site, of all places, when you are dead wrong about something I would expect many people here to know.
I don't have an iPhone to compare it to, but the Nexus One IS laggy, especially when notifications are coming through for a new email, text, or whatever.
I wouldn't say they were playing catchup but other phone os's used multi-tasking as a way to diff them with the iphone. An intuitive alerting system would be just as effective in a consumer device as allowing 3rd party apps to multitask. I'm also guessing if apple does open up and allow 3rd party apps to multi-task they will place some caveats in there to make sure it doesn't drain the battery or slow the UI w/o intentionally doing so...
I'll second that. Tried the Droid, G1 and Nexus One, and still prefer my iPhone 3G.
Why bother
That's great. Good thing the iPhone has a halfway intelligent notification system, isn't it?
I think Steve Jobs was just waiting for CPU/memory/battery capacity to catch up to the point where multitasking will be smooth enough that he's happy with it. He's a control freak and a perfectionist, and if something doesn't work just right, he'd rather omit it altogether than include an inferior implementation. That's why Copy & Paste took so long to arrive on iPhone OS.
I'm still using an original 2G iPhone, and I'm wondering whether iPhone OS 4.0 will be able to run on my device. Steve might decide to disallow it if the multitasking performance is not up to par on older devices.
and artificially disabled from day 0.99. Funny how people always forget this.
Calling someone a "hater" only means you can not rationally rebut their argument.
If it took 2 years to get Copy and Paste right, expect multi-tasking around 2230.
Youre right about one thing, Steve Jobs is a control freak and why would a control freak give up any control.
Calling someone a "hater" only means you can not rationally rebut their argument.
iPhone OS is Unix. It's had multitasking disabled from day one!
mod parent up.
You're on the right track. Steve Jobs Actually didn't include it because it would cost money he was using to feed the homeless.
Since when does allowing multitasking inherently slow things down? Obviously it doesn't; it only slows the system down if you run too many simultaneous apps.
In a real emergency, we would have all fled in terror, and you would not have been notified.
Oh great ... now I'm only going to have crappy 2-3 day battery life like every other multi-tasking phone I've ever owned.
or else!
With rare exception, programs in the background are consuming little or no power in Android. This is Linux after all... a program that's not doing something or waiting to do something is sitting on a wait-task queue... it's not consuming any power until the thing it's waiting for (a timer, an I/O event, etc) happens. Sure, it's possible to write an evil application that sucks power in the background... I've seen one of these since I started using Android five months ago. The small win with multitasking is the ability to very rapidly switch between applications. I do this all the time, and it's dramatically more efficient than on any single tasking OS, like PalmOS or iPhoneOS. The big win is intentional background processes, eg, daemons in Linux-speak. So any application can stick around and do its job, monitoring other forms of communications, checking the weather, tracking or changing settings based on locale, or simply offering me the same ability in any old program (Pandora, Museek) that Apple reserves for just their apps on the iPhone.
-Dave Haynie
I think my Droid is as snappy as the best of the iPhone line, at considerably higher resolution. Your Nexus One goes a step beyond that. And yeah, there are Dalvik improvements on the way. Nothing like an OS tweak to affect every application... Palm did this, twice now, with their WebOS (most WebOS apps are writting in JavaScript!!). Apple's playing catchup, or at least they ought to be, on a number of things. Multitasking is just one... how about screen resolution? Their treatment of the iPad, with its "run iPhone apps in the 480x360 naive mode" hack, suggests that they have no intention of supporting anything other than 480x360 anytime soon. That's fairly tragic... every modern top-of-the-line smart phone now has 800x480 resolution, or perhaps a bit higher. Also, the rumor suggesting an "interface for switching between apps" does suggest some weirdness... how about background tasks? One of the main strengths of Android is the ability to run many tiny daemons, so you have realtime updates of anything you care to update. There's no switching-between, other than in the usual Linux sense of multitasking. If developers can't reproduce any feature Apple can (as one can relative to Android and Google), the OS is still crippled.
-Dave Haynie
Is the "shit at work" app in the Android Marketplace?
-Dave Haynie
Multitasking is a natural concept... it's the single tasking in any OS that has to be learned. Apple's been very good at teaching this as an acceptable limitation, to the point where the iPhonies defend this as some kind of intelligent choice, despite the fact their batteries last no longer than those of my Droid. I'm sure if Apple does introduce some kind of application multitasking, they'll be back to explain to us all why multitasking is suddenly A Good Thing, even though it wasn't in the past.
-Dave Haynie
Given that internet use on the iPhone is a flat $30 per month, this doesn't make AT&T any money. But yeah, that'll happen... there are hundreds if not thousands of apps on Android that can live in the background and do something interesting via the net.
-Dave Haynie
As opposed to the previous MS-OS for phones, which could play 3D games? Yeah, this is "Windows Phone 7", which is apparently what happens when you turn the Zune version of WinCE into a cellphone OS, rather than the old PalmPC version of WinCE (eg, the basis for Windows Mobile). They completely changed the GUI, so it looks, well, just like the ZuneHD... probably better for consumers, and definitely better for finger-touch interfaces, than the old WinMo.
Of course, one might also view this in a negative light. This is Microsoft once again copying Apple, turning their MP3 player into a phone. And it's also kind of a "Hail Mary" pass... the old WinMo has been steadily losing market share. So they introduce this new version of Windows for phones, which requires a totally new API. Old code won't work in the new OS, period.. as Gizmodo put it, "Windows Mobile isn't just dead, the body's been dumped, buried and paved over by a rainbow brick road." You have to write you apps using Silverlight or some other Microsoft nonsense... none of the old WinMo stuff is carried over. Check it out here. MS at least understands that WinMo was so far behind, the only way to catch up with iPhone and Android was a clean, new, Zune-shaped slate.
-Dave Haynie
YEAH! Why have a cell phone.. I think there are pay phone things somewhere... I saw one on Superman.
Laugh all you want but Superman isn't going to change inside his iPhone anytime soon. Even if it multitasks.
Apple obviously still has a long way to do.
May contain traces of nut.
Made from the freshest electrons.
Jobs has a vision for his products and if that vision limits functions, so be it.
Computers get hot so a fan is needed, but Jobs didn't like fans so the original Mac didn't get one.
Transferring files from one computer to another without using a network was an important capability at the time that the NeXT computer was introduced, but it would have compromised Job's vision, so it wasn't included.
If including a standard cut/paste option would logically require a real physical keyboard, than Jobs will convince himself (and his most loyal customers) that copy/paste isn't needed for the iPhone.
Later when it is obvious that most people think copy/paste is a necessary function, Apple found a way to shoehorn it in.
There are a few apps that don't need much more than the very basic notification system that the iPhone already uses. Then, there are a few apps (like music players) that absolutely require full-fledged multitasking. (It'll be nice to finally be able to listen to pandora while checking my email.) But there are a lot of apps that could get by with something in between: a more robust notification system that lets the app register for notifications from the OS when certain conditions are met (example: notify when a phone call comes in, or when the phone enters a geographic area, or connects to a particular wifi network), and run arbitrary code when that happens. This can give the best of both worlds: an app that runs whenever it needs to, but can't waste battery power the rest of the time, even by accident. I wish there were an API that allowed developers to do this.
We're not talking about the Unix process model, are we? We're talking about the iPhone multitasking capabilities. What you and a million other idiots don't seem to understand is that just because the iPhone OS is based on Unix, doesn't mean that the iPhone supports multitasking in a way that is meaningful to end users. If it did, we wouldn't be having this conversation, would we?
Similes are like metaphors
The first two are valid, but the last is bullshit. Of course Apple wanted copy and paste on the iPhone, but to implement it and have it work crappy is worse than not implementing it at all. It may be acceptable in a niche device, but it would compromise user experience. And Apple really cares about user experience.
So you really think that cut/paste was such a challenge for Apple that they couldn't put it in the original iPhone? It's not as if they had to rush the thing out the door in June so that they could sell them for Christmas.
can it tether?
-I like my women like I like my tea: green-
Yes.