I wonder how the new multitasking system will work...What things won't be able to run in the background?![]()
They should do something about the slow startup and shut down times, my old PB on 10.5.8 does it faster than 10.8
Oh, and a new file system, ZFS or similar.
I try to give Apple the benefit of the doubt when most people bash the company, but I have to say, features like multi-monitor support for full screen applications should have been done right from the beginning, or at the very least made right in OS upgrades like Mountain Lion, when they had already had more than enough time to review customer complaints, analyze the technical aspects, and test any improvements. That being said, I'm looking forward to the new features described in the article.
Hopefully my 2008 aluminium MacBook will still supported.
Logic X? No? Ok![]()
wait... so are you seriously saying that safari... will be... "snappier"?
Multi-tasking method could be either good or bad - but better not be as restrictive as iOS by default.
It would be great to have an application that is idol to be persisted to disk. But please, no automatic closing of applications.
Great to have the focus on power uses.
Which subfamily of Felidae will it be this time?
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.
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.
No iWork or Aperture?![]()
It's because of Steve and his protégé Scott Forstall that we have iOS littered with fugly skeuomorphism. I wouldn't be surprised if Ive has hated the UI for a long time but because Steve liked it (and in Steve's world Ive was hardware design only) he had no ability to change it. Based on the rumors from Gruber and Rene Ritchie I'm cautiously optimistic iOS 7 will be a lot more visually pleasing.Agreed, but it may not necessarily be about having time to do it, it may have been upper management such as Steve Jobs who didn't allow for such elements to be included. Remember, although Jobs knew what to do in terms of envisioning a great OS for the Mac, he was very strict on how he wanted it to be operated and some of his decisions left me baffled. For example, I never thought they'd get rid of those ugly aqua scroll bars in OS X. Been there since 2000 public beta all the way to Snow Leopard, yuk. Sadly after so much progression in OS X there are still parts of the OS that have aqua.
Cook may not be the visionary that Jobs was but it looks to be the case they he is more open to making changes and fixes that needed to happen that Jobs otherwise may have not approved of.
Not keen on the idea of iOS-esske multitasking... seems a little pointless on a computer. I'd prefer my apps just to run normally in the background.
It allows a different design methodology where you can assume that anything your app is doing will be in the foreground 99% of the time. You don't have to worry much about hogging resources as a background app, you just have to tell OS X when your app can be paused and it will do so.
It seems about time the Finder got looked at. It's been feeling years behind other OS components. Is anyone else tired of double-clicking the little grab bar that makes a column width actually show a whole filename? Hoping that also gets a review.
You do realise I was posting about automatic termination and not this backgrounding API?
Automatic termination means if you don't have a window opened the app can probably close because it does nothing and starts so fast that you don't see a difference.
So why do you have something against it ?
You won't lose your work ?
It saves you cpu and battery power and also memory
it removes the need to manually close the application.
At least unless you are a moron of developer who can't set the flag correctly on his app
I was struggling to think of why I'd ever need tabbed Finder, but I can come up with a couple use cases. The majority of my Finder usage would be un-tabbed, however, and rightly so.