One you missed: really horrible auto-correct feature Apple added. It will replace a word when you're in the middle of typing it. Completely broken and totally transparent. At first, I thought that WriteRoom was just buggy.
Oh, and the "Home" folder isn't exposed under the Favorites section of Finder by default anymore. You have to go to "Go > Home". Took me a little while to figure that one out.
It must be so automatic to me to go to Finder >> Preferences >> Sidebar and check / uncheck stuff that I didn't know Home wasn't checked by default.
This no longer exists and there's no excuse. Autosaving doesn't even do the same job.
Here is how it used to work: You open this old document because you want to create a new one and use the old one as a template. You either Save as right away or (much more likely) you edit for a bit and do a Save as at some later point.
If you do this with auto save you are fucked. (Well, not really. There is now Versions, so starting with Lion this is finally a recoverable mistake.) Editing your document for a bit before doing a Save as with auto save is the same as mistakenly saving your document – overwriting your old document – instead of doing a Save as. That mistake is catastrophic – I know it, I used to make it often enough myself – and users would make it all the time had Apple left Save as in.
Now when you open an old document you will be asked – as soon as you start editing – whether you want to edit the document or duplicate it, thus avoiding that catastrophic mistake. You can also duplicate documents at any time.
The transition period will be painful, that’s for sure, but the end result is pure bliss. It’s worth it.
A lot of changes with Lion are just like this. Sometimes some pain while transitioning is the price for awesomeness.
It sounds like that work flow just got massively tedious.
One step turned two. Worse? Yes. Tedious? No. It’s worth it given the other conceptual changes and the fact that this is very much an edge case.
Like this I have one copy that I can edit and is always up to date on my main HDD and I have a whole record of copies on my backup HDDs. If I want to see how I edited chapter 3 whilst I was writing chapter 6 (they're related in the plot) I can.
I can't imagine this being something unknown of in the use of other applications. A franchisee that tracks various performance metrics each hour/day on a rolling database (month/year) sends a copy at regular intervals to the franchise owner/manager so that general franchise performance can be evaluated will have the same problem.
I can see how Duplicate -> Save is "only one click more", but the one-click solution worked well. If the "paradigm shift" is related to auto-saves, why not simply have the auto-saves create a new hidden file by default. Either the changes are saved (cue overwriting of the opened file), or the changes are saved as. If the user exits without saving, the hidden file can be marked for auto-delete in X days/hours, making erroneous exits recoverable. If there's a crash/loss of power, the hidden file is prompted for recovery at the program's next start.
The only reason I can think of for not having this is so you could make temporary changes to a document and not have them saved - which just seems to be a different way of arranging the cart and horse compared to the 'save as' workflow. With the Save As workflow, temporary changes are simply not saved. With the Duplicate workflow, you have to dupe the document first to avoid unwanted saving, then make your temporary changes. I don't see much of an improvement overall.
It used to be the case that users had to actually make a mistake in order for this to happen (i.e. they had to forget to do a Save as and do a Save instead – that happened to me way too often, though), with auto save they would make that mistake automatically and every time.
I think what Apple could do is add a “Duplicate and save” function, I don’t think Save as is salvageable with auto save.
I get where they're going with this (iOS-y) but this is just a horrible neither-here-nor-there solution. Dual monitors makes it a true joke.
3) The green maximize button still doesn't maximize.
This isn't and has never been a "maximize" button. It's supposed to zoom the window to fit the content as best it can without scrolling. It's up to the developer to implement it properly with their own logic.Hell, what proportion of them use desktop-variety computers?
I maintain that people think of multi-windowed UI in terms of windows first. Resizing a window to fit the content makes less sense than resizing the content to fit the window. People also seem to get really upset when UI interaction isn't consistent, and the Mac approach means that it varies wildly between apps.
1) Agreed, this can be annoying.
2) The buttons are visually smaller, but have the same target click area.
3) It behaves the same way it did before, so this isn't any worse.
4) The new scrolling takes a day or two to get used to, and then is better. If you really don't like it, there's an option to toggle it off. This isn't an issue.
5) Agreed, it is arguably slower and tends to drain the battery faster. It's also doing more. It sucks, but that's the price of progress.
6) As I see it, FireVault is a huge plus and not at all a drawback. Was there anything 'terrible' about the process other than that it was lengthy? And really, a one-time conversion cost for such a huge improvement to this feature was a problem for you?
7) This happens with practically every desktop OS upgrade ever and, as you mentioned, isn't a problem anymore.
So besides #1 and #5, are there other real complaints?
I'd personally add "really botched multi-touch gestures" to the list, but I'm genuinely curious if it's actually that much worse or people are just piling onto this rant.
You now duplicate and then save.
They don't learn until they've been burned, probably quite badly. If the computer doesn't HAVE to burn them in the first place, why should it?
Um, that?
The concept of "save" was good for a time, but having everything autosave is absolutely forward progress.
My Macbook Air just kernel panicked about 20 minutes ago (which, admittedly, shouldn't happen). I had to hold down the power button, and then turn it back on. Less than one minute after the crash my laptop's state, opened programs, tabs, files, unsaved progress, was restored.
Auto save is an obvious improvement. The whole saving paradigm sucked and I’m so happy that Apple is tackling it.
I would say this is exactly the problem they are trying to fix.
1) Removed? It's still in there for office and photoshop
2) Never really need to minimize, use mission control
3) Have no use for that green button, use full screen apps
4) Coming from Windows, learned reverse scrolling in 15 minutes, now the other way feels strange
5) Can't really address this, this macbook air is by far the fastest computer I've used
6,7) Haven't noticed these
1) Removed "Save As". You now have to duplicate and then save the file.
2) Smaller resize/minimize/"maximize" buttons.
3) The green maximize button still doesn't maximize.
4) Switched default behavior with mouse scrolling.
5) Generally slower and more resource intensive, noticeable on older (2009) Macbook Pros.
6) Terrible, lengthy switch over from the previous version of FileVault, if you had that enabled.
7) Crashed a lot of programs initially, especially Chrome. Now not as much, but very crashy a few months ago.