Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
A faster Safari? They've said that with every update, yet youtube is painstakingly slow still.
 
Craig Federighi: "with new multitasking you can focusing to do task one at a time, amazing huh?"
*applause*
 
Most folks don't need it when you look at power users v common ones. What that vast majority needs is a system that doesn't crash because Safari is a
RAM hog, or time machine backups not working, or wifi that is crapped out by an update etc
Sure there are issues to iron out, however you can't dismiss multi monitor support as a power user issue. It is a "feature" many of us have been frustrated with for some time.
Heck the common user doesn't typically even use the fast switcher in Mac OS even though its been there for generations and its the essentially the same keystroke as Windows. (Yep there's a fast switcher already)

Which of course has nothing to do with multi monitor support. It always amazes me that people will dismiss a feature they don't use or need as a "power user" feature even though it may not be power users using it most of the time. Multi monitor support is very much a mainstream feature valuable to many.
 
OS X uses some of the most advanced multi-tasking in the industry. It sounds like Apple wants to limit some of the pre-emptive multi-tasking capabilities to mimic how iOS does things. How is this a good thing? Multi-tasking on OS X already works just fine, why fix it when it ain't broken?

For energy efficiency purposes on portable devices. This wouldn't impact a system with a direct power connect to a non-battery solution. For instance, if you have a system with a DVD drive that is running an app in the background and you aren't viewing it the power is slowly drawing down the system. Suspend that application's energy draw until its direct use on apps that require playback is one example.

Obviously, if you're doing a DVD burn it doesn't make sense for the system to suspend the process in the background. The system has to determine what types of processes are being used in the background and change their priority states. Within certain priority states they will have to categorize them as a suspend to protect power draw or not.
 
Maybe people say ¨safari feels snappier¨ because they restarted their computers after the installation and it was the first time in months, and safari actually, in those cases, would indeed be ¨snappier¨.
..anywhooo...

Nope! Safari has improved dramatically over the years.
 
Completely false. All apps are still in memory, all their data is still in memory, and they don't have to be restarted when you switch back to them. Until the OS stops the app completely, in which case it is removed from memory, and when you switch back it is restarted and has to run all kinds of code to get back to the same state.


You should really go back and watch the iOS 4 intro. You're right, all app info stays in memory but it is all frozen until you switch back to the app. In other words, they don't "stay running." Only 7 services stay running. In general, most apps don't use those 7 in the background.
 
Nothing wrong with having multiple ways of doing things. I mean, you don't actually see two icons at once - the dock disappears when you enter Launchpad. So there's not really any confusion there. I use them both - I could live without Launchpad, but the dock is a must.

You're wrong. The dock APPEARS when you open Launchpad. Even if the dock is set to hidden, it pops up with Launchpad and you see duplicates of all your apps. Poor design IMO.
 
I can see myself being the only one who will like the background app pause feature. As long as the app can send low level info to you I'm all for it. Imagine how much battery life is spent with background apps running.
While I can see this being helpful to some users it would be a disaster for my MBP usage. In fact when I reach for my MBP it is to leverage its multitasking abilities over my iPad.

Frankly I don't think Apple would be so stupid as to implement this in a way that the user didn't have control. When you have apps running in background for hours at a time the last thing you want is for the system to suspend them.
One thing I want to see out of 10.9 is more of a unified UI. No not iOS on a Mac, but having cross platform icons and settings.
It doesn't bother me to much at the OS level. What I'd rather see though is far more work gone into unified apps such as iWork and others. We need iWork versions that use exactly the same files as stored on the cloud. Solve that problem and other I could problems and we will move beyond the era of iCloud being useful "only if" it was usable.

As to iOS and Mac OS, people still don't grasp that they are the same OS underneath the GUI. However features that make iOS a rest mobile solution are really the opposite of what you would want on Mac OS.
Using apps on both Mac and iOS. Just more seamless connection between the two devices.

That should be an issue of syncing. I'm actually rather please considering how well the two work together now. Future improvements are likely to be incremental.

As a side note I can see IOS becoming far more powerful in the future as hardware improves to support more advanced features. I suspect it ip will be far more likely that iOS will get major updates in the coming years.
 
"Ability to keep a dedicated Space or full-screen app open on a single monitor within a multiple monitor setup"...
It would be very nice if :apple: can (finally) get that working, I believe it when I see it :rolleyes:
 
You're wrong. The dock APPEARS when you open Launchpad. Even if the dock is set to hidden, it pops up with Launchpad and you see duplicates of all your apps. Poor design IMO.

Duplicates? All you see are the icons. It isn't hard to understand that the dock is a place for apps or folders that you want to have quick access to. The Launchpad is the place for all of your apps including ones in the dock. One a mobile device, that's too many UI layers to have duplicates. But on a laptop/desktop, more UI layers are welcome and make more sense. Let's not forget that on Windows and Linux, you see duplicate icons of the same app in many places. It's more flexible and provide multiple ways to accomplish the same goal. On a mobile device, too many ways to do the same thing is confusing and not at all efficient due to screen size, fewer navigation methods, etc.
 
i hope they fix the expose gestures. the 4-fingers-up-to-reveal-desktop and 4-fingers-down-to-show-all-windows worked so much better. Right now it's so much more of a hassle to move files from a window to the desktop with the "pinch out" gesture

God no, please do not do anything with that. I love it the way it is now.
 
Rather than dumping a laundry list of everything that you can possibly think of that you dislike about OS X, you might actually provide feedback directly to Apple. Apple is, similar to Snow Leopard, producing a release that improves on the core OS, at least it would appear. CAN WE CHEER APPLE ON FOR ONCE IN A LIFETIME? This could be a great thing...

PS: I'm a pragmatist, and I'm not suggesting that people fawn over something they shouldn't. Yet Apple would appear to actually be giving people what they would seem to be begging for: Power User TM features. Since apparently everyone is now an expert and a Power User TM. Maybe we can cut them just a little slack for once...
 
So, it took Apple 2 years to bring support for multiple monitors? That's very innovative, should have been there since OS X 10.7.1 at the latest.

I've had multiple monitors in 10.5, 10.6, 10.7, and now 10.8. Works perfectly for me and always has. I never understood why people claim it doesn't work.

Hit the green plus to maximize it to the screen. Easy.
 
Duplicates? All you see are the icons. It isn't hard to understand that the dock is a place for apps or folders that you want to have quick access to. The Launchpad is the place for all of your apps including ones in the dock. One a mobile device, that's too many UI layers to have duplicates. But on a laptop/desktop, more UI layers are welcome and make more sense. Let's not forget that on Windows and Linux, you see duplicate icons of the same app in many places. It's more flexible and provide multiple ways to accomplish the same goal. On a mobile device, too many ways to do the same thing is confusing and not at all efficient due to screen size, fewer navigation methods, etc.

Well the dock itself is in fact a "launchpad". If anything, Launchpad feels like a forced way to bring an iOS feel to OS X. If you wanted a launcher of all apps you could always just add your Applications folder to Stacks and voila. If they really want to keep Launchpad, I don't think I should see two icons for Safari, two for iPhoto, etc etc. Just seems unnecessary.

If you say it's a good thing, why not toss some app icons on the desktop and status bar. That would provide even more ways to open Safari:rolleyes:
 
Completely false. All apps are still in memory, all their data is still in memory, and they don't have to be restarted when you switch back to them. Until the OS stops the app completely, in which case it is removed from memory, and when you switch back it is restarted and has to run all kinds of code to get back to the same state.

Yes they do stay in memory but they use basically the minimum amount of memory needed. They are "frozen" in memory. Unless they are using one of the background services they can not run in any operation, request more memory or anything. They're just there. Yes they are in memory though they use the least amount of memory needed. So yes they are still in RAM though the OS can at will get rid of them if it wants too.

Same apps actually don't even really do that. They have their own way of doing it sort of. When an app is closed they do like a "quick" save sort of thing which saves the state you were currently at in the game/app. That way when you restart it, no matter when you do, you can continue where you left of. They only have to reload the resources since those won't be in memory anymore. A lot of games do this. I know a game I play uses this. It acts like it is reloading from the very start, and it is, but is finding your last save and resources to reload. Then it starts back up basically where you were at.
 
...

Frankly I don't think Apple would be so stupid as to implement this in a way that the user didn't have control....

Hah!

Look at iOS. The lack of multitsking is one of the main complaints from anyone who has ever used anything other than an iOS device, but Apple is too cheap and too lazy to rewrite the code written close to a decade ago, so they keep spinning the tale how they do it for the good of the consumers. BS.

Apple may not be so stupid, but they sure think iOS users are.
 
Probably similar to iOS, on a voluntary basis: If your app is moved into the background and doesn't show a user interface anymore (that would happen if another app runs in fullscreen mode), it is told about that; it stops doing things that it shouldn't do in the background (like iPhoto showing a slideshow would be pointless waste of CPU time if the app is in the background), it prepares that it will not get any CPU time unless it asks for it, and it saves its state to the disk so that it can be stopped and restarted if the OS decides to do that.
Which is great for a memory and processor constrained system. Often it is not what you want to happen on a desktop system.
Another iOS feature that is missing on MacOS X: In iOS, when the user quits an application, that app can continue finishing its work, even though to the user it looks like it has exited. That doesn't work in MacOS X currently.

I'd have to think about this one. Most of the time on Mac OS when I try to quit an app I want it to do so right then and there.
Don't confuse "multi-tasking" with "running multiple apps in a way that is best for the user". Multi-tasking is easy. Doing what is best for the user is hard, you get screamed at by people who don't understand it, but your users are actually happy. The point here is to pause background activity that shouldn't happen and is a waste of time, as opposed to background activity that _should_ happen.
This is a huge problem. For example how do you know when something shouldn't happen. One item already mentioned is slide shows in iPhoto. Maybe the user wants a slide show going on in the corner of a screen even if iPhoto isn't the foreground app. It might not make sense to stop an app that isn't visible either as that introduces significant app start up delays and lag when it does come into view. To put it simply people have different expectations.
Actually, it is very, very good. It just doesn't do things the way that some programmers have learned and can't get out of their minds.

Baloney. It isn't a matter of what programmers want but rather what users want. To that end iOS multitasking is far from perfect. The best option that I can see is for Apple to offer users a way to designate the operation of an app in background so that the user can choose to do so when needed. One example would be a market watching app that is always in background updating portfolio information and is always ready to regain the foreground. In a nut shell something that is allowed the same functionality as that of the E-Mail app. Another example would be an app collecting data from laboratory instruments over a period of time. Such an app need to be able to run in background with no interference from the OS over a long period of time.

Somewhere in between all of this Apple needs to expand the ability of iCal to run apps on a regular schedule. For example start up a "newspaper" app at 5:00 am to have it downloaded for breakfast. In effect give iCal some of the capabilities that is common to cron on unix systems. Obviously iCal can multitask to do this but a use could have multiple jobs to prep for the start of a work day. I use the word newspaper above because it is a simple concept for people to understand even if newspapers are a dying breed. The concept though is applicable to any number of data transfer issues, be it sales reports, the latest pics from Hubble, a magazine subscription, production reports, or anything that needs to be downloaded and prepped on a regular schedule. The point is these are apps that would need to multitask to complete their jobs due to the asynchronous nature of their operation.

This iCal as Cron feature is something I do hope that Apple is working on along with robust scripting. Being able to wake up in the morning and grab an iPad off the charger ready for the day would be a huge sales advantage. The reality is network lag still sucks and that isn't likely to change soon. If the first hour of your day off the charger doesn't significantly decrease battery life then iPad will find even more usefulness than it already has.

In a nut shell iOS needs improvements to the way it multitasks and the way the users can interact with that capability. It is all about the user.
 
There are so many little things that I am used to doing on my old Google Nexus that I can't do on my iPhone 5, it's not funny.

I am sure everyone has their own apps they want running in the background sometimes, but in my case I run into iOS's limitations if I use an app like flashlight, or a training app, etc., and then I want to send a text, make a quick call, change a song or a podcast and so on.

It's an idiotic limitation and it is even more idiotic that Apple gets to decide which apps it will allow to run in the background (usually its own apps, plus a handful of third-party ones).

If WE (the users) had a choice to decide which apps can run in the background, you wouldn't be hearing so many complaints.

Consumers are a fickle bunch and iOS can go from being on top (and it has already lost that to Android) to struggling like BB in a matter of a year or two, if it doesn't keep up with the competition.

And as far as touch on OS X, I am sure there once were people who said that nobody needs touch on their phone, too.

Touch is available on Windows and it has brought some pretty innovative designs to the laptop world. Chrome is coming out with touch this year (if I were Apple, I'd actually worry about Chrome, because just like Android, it may come to bite in a year or two).


And those little things are?

Besides the flashlight one the others will be saved in memory so what? what exactly are you losing by it?

the developer can request up to 10 minutes of run time after a user takes that app from foreground to background to finish what its doing, so if they implement it you won't lose anything from your training app,again its a matter of the developer doing it(see the difference?)

oh really? the same Apple that is selling more and more every year? lost marketshare due to the crazy amounts of low-end androids. Apple is still at the top of profitability and its brand is very powerful,especially the iPhone and iPad brands.

you already have touch but really touching your screen? imagine you have a 27'' iMac,are you really going to stand close enough to it to touch all of the screen? unless you have large arms i don't thinks its a very good idea,especially if people have to use it an entire day it will probably make your arm very tired and you require a redesign of OSX to something with large icons as your fingers just don't have that great of accuracy for the small icons now used.

what such innovation is that? hybrid devices? that already existed,only now windows has been redesigned to use it properly. Chrome? really? should apple be worried about the ChromeBook too? as long as Chrome requires an internet connection and uses the internet for basically anything it won't have that great of a success.


People have been doomsday'ing apple since the iPhone 4S release although i believe they'll go through a rough patch in 2/3 years that will be due their astronomical growth from 2009 to 2012 which is something that no company could maintain indefinitely
 
Hah!

Look at iOS. The lack of multitsking is one of the main complaints from anyone who has ever used anything other than an iOS device, but Apple is too cheap and too lazy to rewrite the code written close to a decade ago, so they keep spinning the tale how they do it for the good of the consumers. BS.

Apple may not be so stupid, but they sure think iOS users are.

What decade old code are you talking about?

iOS is fully multi-threade multi-tasking. The OS enforces suspension and termination of background apps (configurable) in order to preserve battery life.

If you've ever done any iOS development you'd know that an app can request to be kept alive *in the background* up to 10 minutes after the user has switched away from the app. Also apps such as audio players are permitted to do pretty much anything whilst they're running in the background (as long as they continue to play music).
 
Hah!

Look at iOS. The lack of multitsking is one of the main complaints from anyone who has ever used anything other than an iOS device, but Apple is too cheap and too lazy to rewrite the code written close to a decade ago, so they keep spinning the tale how they do it for the good of the consumers. BS.

Apple may not be so stupid, but they sure think iOS users are.

The funny thing here is that I own both products and frankly the limitations seen on iOS aren't a huge problem on my iOS devices. Yes there needs to be improvements with multitasking under iOS, I'm not saying iOS doesn't need such improvements. Rather the problem is that these features on Mac OS would be far more problematic and not in the users best interests.

It comes down to the way I use the two different systems. For me iOS like multitasking, without user control, would be a complete disaster on Mac OS. IOS is a completely different platform that I use in completely different ways. So while multitasking isn't perfect there ( it does exist) it isn't the big problem it is on Mac OS.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.