Aaaand fuck.
Aaaand fuck.
OK, sure, with two monitors, it renders the second display useless. I get that.
So why don't you just not use fullscreen mode, and continue doing everything you've been doing with dual monitors since the days of OS X 10.0 ?
You lose nothing, and gain nothing, so it makes absolutely 0 difference in your workflow.
It does to some people. To steal from my comment a few days ago:
"I could care less about Apple's Fullscreen API -- what I hate is that apps are replacing their old Fullscreen behavior (like Chrome has) in favor of the Apple standard. Which led me to make this comment on a Firefox 12 HN post a few months ago: "... it will be a shame when they implement full screen if it takes away the current layered option. Firefox is the last major OSX browser to work in fullscreen while still allowing apps to be above or below it. With Moom's hotkeyed window positions--it's extremely convenient to bring a text editor to focus and still be able to scroll the web in the background. Mozilla, please don't let this happen!" Apple's Fullscreen API just seems like a lazy approach to delegating UI real-estate and the last thing power-users would want."
1. because it's garbage
2. because applications which used to have a working fullscreen mode — such as firefox — and get converted to the Lion API result in no gain and lots of pain
> So why don't you just not use fullscreen mode, and continue doing everything you've been doing with dual monitors since the days of OS X 10.0 ?
Like use fullscreen mode on Firefox, which has been there forever? Oh wait, now I can't. Just as I can't use fullscreen mode on, say, Quicktime X. Or have movies display on the big screen. I didn't really want them on the 27" anyway, the 15" is so much better isn't it? Pulls you closer to the screen, unless you don't care for the picture.
> You lose nothing, and gain nothing, so it makes absolutely 0 difference in your workflow.
Yes actually: Firefox still had a fullscreen mode which actually worked correctly. Now it does not, unless there is some sort of hidden setting able to toggle back to the "old" API as there is in VLC.
>2. because applications which used to have a working fullscreen mode — such as firefox — and get converted to the Lion API result in no gain and lots of pain
As a Macbook Pro user, I've been looking forward to Firefox's implementation for a while. Applications that take advantage of Lion's fullscreen API allow me to easily swipe between multiple apps with the trackpad, which make using a laptop significantly nicer without needing to use an external mouse.
It is essentially broken for people who have multiple displays and Apple sucks because of it. But it's not broken for everyone and provides significant functionality for a lot of people.
It doesn't fix the fact that you're left with one (or more) useless displays in full screen mode, but it does let you choose which display to do the full screening on.
It's better than Lion in that you will be able to choose which of your displays is used to go into full-screen mode, rather than always just using the 'main' display.
Disclaimer: I haven't actually tested in Mountain Lion, but this is the only consistent explanation I've been able to gather from careful reading of people's complaints and Apple's description of the feature change.