You can have the same feature for the end-user on both computers (the feature being smart multitasking) even if they run differently. Problem solved.
If someone told you that Windows machines and Macs both have the feature of 'file management' would you pipe up and say they are different features because they do it differently? Maybe you would.
Like I said, depends on the implementation. The way Apple's been going these days (hello? No "save as"?) I wouldn't put it beyond them to completely **** this up, at least in the first iteration.
Clearly you never move files from one folder to another.
Fix the "reload when going back a page" first, please.
I'm hoping for the same, but I'm not expecting it to be supported. Damn fine machine - 5 years old and still runs beautifully.
A big question is what macs will they drop support for? At this point they're down to all 64 bit machines (including 64 bit efi) so what will the next cutoff point be?
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.
Glad to know, Safari will be faster, when I use it to download Firefox and Chrome.
I hope, you can turn off background suspend. When you have a process that will take days to run, you don't want to freeze it, just because you want to check something on a web page.
It would be nice, if we could set the priority of background and foreground tasks. Lets say, 95% background 5% foreground.
Yeah I figured as much. I guess we will find out exactly what the name will be at WWDC![]()
Just to be clear, you, splitpea, believe that Apple would implement multitasking which prohibits any background activity (beyond maybe alerts and audio streams from iTunes)? Because that's what I've been responding to. Or does "I wouldn't put it completely beyond them to @#$% it up, at least in the first iteration" now mean something different? (You really hedged your bets there btw)
...
Today's report also indicates that Apple has been working on new ideas for multitasking that could be included in OS X 10.9, drawing some inspiration from iOS....
Oh dont you know, it will be
OS X Tabby
The purpose of launchpad is not to roam around in it. It is to pick a target, hit it and get out. The faster that is done the more effective the application is. Smaller icons doesn't necessarily improve that traversal speed.
Might be time to ditch the beloved dock. Launchpad does the same thing and the two of them together are very redundant features.
Plus, the dock has always taken up unnecessary screen real estate when it's only needed some of the time. Yes, you can hide it, but that's not on by default. Just go with the iOS-y Launchpad and save the pixels at the bottom of the screen for something else.
Apple needs to simplify the OS again.
The downloading process is confusing to newbies.DMG, eject, etc is ridiculous. They should automate opening a download and simplify it like it was before OSX.
There are other areas that could use simplification as well. The scroll arrows should be returned to an option of having them on both ends.
Rubbish. The algorithm that decides when apps should or should not go is an Apple algotithm.
If an app can be automatically terminated is dependent on developers. When and why any given app is terminated if the OS has permission is down to the OS.
There are plenty of devs who are morons.
If Safari is content to lose data and corrupt downloads in this way, why should I trust that Apple apps will terminate properly and are coded correctly without losing data?
Not really, I have both to burn and I am better off manually managing it.
To support automatic termination, you should do the following:
Declare your apps support for automatic termination, either programmatically or using an Info.plist key.
Support saving and restoring your window configurations.
Save the users data at appropriate times.
Single-window, library-style apps should implement strategies for saving data at appropriate checkpoints.
Multiwindow, document-based apps can use the autosaving and saveless documents capabilities in NSDocument.
Whenever possible, support sudden termination for your app as well.