5 ms·
For those criticizing- He has given one example of what he thinks is wrong. Not all posts are meant to be essays... Briefly though, (as another user who switch
by hackoder 15y ago
For those criticizing- He has given one example of what he thinks is wrong. Not all posts are meant to be essays...
Briefly though, (as another user who switched from Mac OS X), I can certainly give examples of what he says:
Not all of these are specific to OS X, its the overall hardware and software that is getting frustrating.
More user-hostile
- If you replace your SuperDrive with another drive, you CAN NOT boot any operating system (other than Apple's) off usb drives or even external DVD drives plugged into usb slots. So with two hard drives, you can not install Windows or Linux. [1]
- Batteries are not considered user-swappable anymore. [2]
More buggy
- Battery life degradation when moving from SL to Lion. Apple forums are full of examples. [3] (78 page thread, no confirmation or fix from Apple).
- We all know how annoying the switch to Mission Control was, right?
[1] http://forums.macrumors.com/showthread.php?t=1125135 http://forums.macrumors.com/showthread.php?t=1125135
[2] http://support.apple.com/kb/HT1756 http://support.apple.com/kb/HT1756
[3] https://discussions.apple.com/thread/3194235?start=0&tstart=0 https://discussions.apple.com/thread/3194235?start=0&tst...
[Edit: formatting]
- ugh 15y ago“We all know how annoying the switch to Mission Control was, right?” No, we certainly don’t. I love Mission control and I think it’s an improvement over Exposé. Don’t pretend I’m agreeing with you. For me personally Lion has been a solid improvement. Quite a few things that used to suck about OS X still suck but I have seen nothing but improvements or neutral changes with Lion. (Yeah, I have some minor quibbles, but mostly about apps I hardly ever use anyway.) I had no technical issues at all. Again, that’s for me personally.
- Tycho 15y agoThe thing about mission control is that they could easily have left the old expose intact as an optional alternative, but nooooo they had to remove it completely and fuck up thousands of users' workflow habits. I mean you have to admit the way mission control stacks windows on top of each other for each application is pretty ridiculous. Other than that it's fairly useful. But there was no good reason to remove the 'all app expose' feature, leaving only the within app expose. They either just overlooked it or want to brainwash users into some sort of app centric paradigm. It reminds of when they released the magic mouse and you could no longer have expose mapped to a third mouse button. Surely wasn't the only user dependent on such a useful feature.
- ugh 15y agoI like the way Mission Control stacks windows. As for leaving unstacked windows in: Yeah, well. That’s not how Apple rolls. Love it or hate it.
- falling 15y ago> But there was no good reason to remove the 'all app expose' feature, leaving only the within app expose. They either just overlooked it or want to brainwash users into some sort of app centric paradigm. Do you mean the "Show all Windows for the current app"? I'm pretty sure it's still there. Might have a different gesture tho.
- Tycho 15y agoNo I mean there used to be two forms of expose - show all within app, which I almost never used (it would only be useful if you had a truly ridiculous number of windows open, really), and show all windows across all applications including the finder. They've taken away the latter, which was the useful one. Most times I hit expose in the past it was to go to a window of another application. For instance switching between the code I was editing in Coda or Textmate to the webpage I was building in Safari, or the graphics I was manipulating in Preview. In fact I did this constantly. Now it's a two step process: select the app in mission control, and then do expose once you're in the app. It wouldn't be so bad if the way Mission Control stacked the app windows wasn't so useless - when you expand them they should at least fill the screen so you can see everything, instead they become just slightly less bundled together, forcing you to footer about with the pointer to get what you want. Expose was one of the best GUI innovations ever, IMO, and they've bloody ruined it.
- gurkendoktor 15y agoTotally agreed. To add more reasons: 1. I don't have money for an SSD right now, and Mission Control can take up to 10 seconds to start, presumably because some stuff on another Space had been swapped to disk. I just used a friend's 800 MHz iMac G4 at a party and damn, Exposé was instant! 2. I don't even want to see stuff on another space. I move apps on spaces to FOCUS, not to see my unwritten report at the top of my desktop when switching apps on one space.
- ramanujan 15y agoWorst parts of Lion over OS X: 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.
- furyg3 15y ago8) Strange full screen behavior. 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.
- adbge 15y agoSeriously, wtf is up with removing "Save As"? I had to copy the text from a file I was working on and paste it into a new file because the "Save a new version" option wasn't doing anything. 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.
- ugh 15y agoSave as doesn’t make sense if the app auto-saves.
- fiblye 15y ago"Save as" is usually used when you want to save it as a different file somewhere else, and most people have cmd-shift-s ingrained in their mind. This no longer exists and there's no excuse. Autosaving doesn't even do the same job.
- masklinn 15y ago> He has given one example of what he thinks is wrong. Most of it being... not smart? > Right now, since I've switched to Gmail, I'm trying to back up and remove from my machine years of accumulated mail storage from mail.app. First obstacle: a user's library files are now hidden. No, the ~/Library folder is now hidden, you can see it via Terminal, by opening the Finder's Go menu with an option-click or browse it because you know the path (cmd-shift-G, for instance). This change is sensible: how often does a user need to go into the Library folder? > Finally find them (thanks Matt Silver), back up the files to an external disk, and then delete them. But then when I empty the trash, an ungodly number of files--going back years--claim they are "in use" and can't be deleted. So here I am having to click "continue" every few thousand files (if I'm lucky) as I page through more than 400,00 files to be deleted. I know this is actually an old mis-feature - but why the devil wouldn't they give you an "ignore" checkbox or a "delete whatever you can checkbox"? This has been a problem for years, but never fixed, while they add new gloss all the time. He hates OSX now because of something which has been there forever? Like the trash refusing to delete open files you moved there? There are issues with OSX and there are debatable changes, but his post is simply nonsense.
- jonhendry 15y agoI wouldn't be surprised if the mail files were 'in use' due to Spotlight indexing. The workaround for that would probably be to tell Spotlight to not index mail. Or else, perhaps, to delete them from within Mail.app?
- mun2mun 15y agoBattery life degradation when moving from SL to Lion. Apple forums are full of examples. [3] (78 page thread, no confirmation or fix from Apple). Wow! 78 page thread! Almost all are saying me too. And no sound in blogosphere! Just imagine if same thing happens in microsoft discussion forum. Tech bloggers really cut some slack for apple.