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.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
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)
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?
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...
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.
For the love of god, I hope they improve "Mission Control."
"Mission Control" is a joke compared to Exposé.
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.
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.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.
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.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.
Using apps on both Mac and iOS. Just more seamless connection between the two devices.
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 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
Hopefully my 2008 aluminium MacBook will still supported.
Pardon my ignorance, but Cabernet is not a big cat![]()
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.
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.
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.
...
Frankly I don't think Apple would be so stupid as to implement this in a way that the user didn't have control....
God no, please do not do anything with that. I love it the way it is now.
Which is great for a memory and processor constrained system. Often it is not what you want to happen on a desktop system.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.
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.
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.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.
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.
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).
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.
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.