Slashdot Mirror
iPhone 4 News Roundup
We have a slew of iPhone 4-related stories this morning, so I'm lumping them together for easier consumption/ignoring, depending on your personal feelings on the subject.
Here is a blog entry proclaiming that iOS 4 multitasking sucks and why. Here is a sketchy summary of privacy violations by Apple and AT&T — apparently they are reporting back jailbroken phones. Skunkpost has a story about the lines and sales of the new phone. But the big news of the morning is the reception problems that apparently only affect people who hold the phone in their left hands.
Possibly not for long though http://www.engadget.com/2010/06/24/iphone-4s-yellow-spot-issue-goes-away-with-a-bit-of-time/
Taxation is legalized theft, no more, no less.
Apple is using a bonding agent called Organofunctional Silane Z-6011 to bond the layers of glass. Apparently, Apple (or more likely Foxconn) is shipping these products so quickly that the evaporation process is not complete. However, after one or two days of use, especially with the screen on, will complete the evaporation process and the yellow "blotches" will disappear. How do I know? I was involved in pitching Z-6011 to Apple.
No one is denying that it exists, its just that it could very well just be the bonding agent not drying yet.
Taxation is legalized theft, no more, no less.
Try again. iPhone apps can't call the equivalent even of Windows 3.1 yield(); - they either run in the foreground, or they're suspended - like the DOS 5.0 task swapper.
Don't be disingenuous. The parent was correct; iOS has a kernel with a preemptive task scheduler, and there are any number of API calls which explicitly yield or do the moral equivalent (any blocking I/O API call). Even while an app runs in the foreground it is always being multitasked with other parts of the system.
Also, by definition tasks in a preemptive multitasking OS either run or are suspended, at the operating system's whim. The difference between that and a system like DOS 5 is left as an exercise for the reader.
The few exceptions need to take advantage of a special api call for music, of all things.
And other 'special' APIs for other things. Apple has tried to come up with a comprehensive list of tasks which can usefully be backgrounded on a smartphone, such as messaging, downloads, and yes, audio playback. You simply register a thread (process? dunno the exact details) as providing such a service, and the OS allows it to continue to receive timeslices (assuming it's not blocked on I/O) while your main application is held suspended because it's not in the foreground. There are significant limits on what you can do in that context, but they all make sense in terms of limiting power consumption.
If you want a real multi-tasking OS on your phone, you won't get it from Apple. Not this year, and not next year. They're already starting to fall behind in the features race.
Oh please. You're smart enough to know that iOS is built on the Darwin kernel, and what that implies about its multitasking capabilities. All the limitations are deliberate and carefully thought out. It's undeniable that they're there because Apple thinks they will provide a better overall user experience, because the path of least effort for Apple would have let users multitask anything on day 1 of the app store going live. Instead they went to the trouble of doing extra work to restrict it.
Argue against the design of iOS 4's carefully limited multitasking if you like (oh no! That would require you to actually inform yourself! Can't have that), but pretending it's not "real" and that they're falling years behind is just trollish.