I could give you so many, but I'll kick off with just three that spring to mind. i] Keyboard navigation is terrible. ii] Tags cannot be applied to symlinks. iii] If you're looking at a tree view, with any number of folders displaying, the only one you can create a new folder inside is the very top-level folder.
My biggest complaint: Normal Copy and Paste does not work. My mother is used to Copy and Paste and it would work in Linux but not in macOS finder because of: think different
Also why are folders sometimes cluttered all over the place and shorts cuts so weird?
Well I fixed it all with Forklift but I also grew up with Norton Commander ;)
What about copy and paste doesn't work...? I use that feature daily.
And for the clutter, you can configure Finder to be more militant in how it displays/orders things.
The only gripe I have with Finder is needing to set up a million QLPreview things to do better spacebar peeking. Otherwise, it's fine - it "just works" and isn't fancy.
I think they possibly mis-spoke and mean cut-and-paste, which does appear to be intentionally permanently disabled in Finder via the menu or shortcut. But you can drag so it's not a huge issue to me. Copy-and-paste works a-ok.
That's not cut-and-paste. That's copy and some weird modified paste that, as far as I'm aware, doesn't exist anywhere else. Why completely break the existing convention?
Because cutting-and-pasting is a destructive action that can lead to data loss.
Under the conventional implementation of cut-and-paste, it's easy for a user to inadvertently cut-and-paste a file, when they meant to copy-and-paste said file, either through a misclick or, by hitting the wrong keyboard combination. This is because:
1. The menu option for cut is right above the menu option for copy
2. The keyboard shortcut for cut (command-c) is just one key away from the keyboard shortcut for copy (command-c) on a QWERTY keyboard
Cutting and pasting deletes the file from its original directory, however under a traditional cut-and-paste operation, the system does not ask for confirmation. Consequently, if a user mistakenly cuts a file or directory without immediately noticing their mistake, their files could be rendered unrecoverable (and keep in mind that there's no particular reason why they would notice... the UI provides no special indication when a file or directory is deleted via cut-and-paste). This is arguably a very bad user experience.
The equivalent action to cutting-and-pasting on OS X is copying, pasting and then deleting the original file. By adding in this extra step, the UI has forced users to acknowledge that their action is potentially destructive and unrecoverable.
Also notice that the command-x shortcut in Finder copies a file. It does not cut the file. Again, this protects the user from inadvertent data loss if they use the wrong keyboard shortcut.
It's a rather unusual move Apple has made here by breaking convention, but I think they've made a wise wager that users would rather be annoyed by a small extra step, then be faced with the loss of important data.
Thinking about this design choice, I now wonder how many times I've had files mysteriously go missing on Windows and other operating systems simply because I used CTRL+X when I meant to use CTRL+C
>Thinking about this design choice, I now wonder how many times I've had files mysteriously go missing on Windows and other operating systems simply because I used CTRL+X when I meant to use CTRL+C
Zero. If one CTRL+Xs accidentally, Windows and most Linux Desktop pickers change the highlight colour before the copy. At worst you can CTRL+Z it after or copy it back. It's not a 'destructive' operation since you always have one copy of the file.
It's a typical case of Apple deciding users are stupid and therefore should be limited, combined with the typical 'just everything Apple does' syndrome.
I take your point. I can't be certain why, because it's been so long since I used Windows, but I never found this to be a problem in practice — maybe I was just lucky. I guess you could make the same argument about cut in any context, except:
a) you could argue that cutting text isn't as destructive as deleting a file, although they could be one and the same if you happen to have an entire file's text selected
b) mechanisms for undo'ing text operations tend to be more sophisticated than undo'ing filesystem operations; I might argue that's a separate problem to be resolved
I'd be perfectly happy if this were an option, buried in some obscure preference panel somewhere, labelled "yes, I really want to shoot myself in the foot" but, as it stands, I don't even get that.
>I can't be certain why, because it's been so long since I used Windows, but I never found this to be a problem in practice
I would have said the same thing. But then again, I'm sure there's been times where files have gone "missing" on my computer. Did I misplace them? Accidentally deleted them? Accidentally cut-and-paste? Who knows.
>I'd be perfectly happy if this were an option, buried in some obscure preference panel somewhere, labelled "yes, I really want to shoot myself in the foot" but, as it stands, I don't even get that.
Yeah, no argument from me there. I'd appreciate an option buried in the OS X CLI at a bare minimum.
If I accidentally cut-and-paste from a text document, the absolute worst case scenario is that I lose the contents of the text in that document. It's a bad situation, but the damage is limited and contained.
If I accidentally cut-and-paste a file or directory, the damage could be immense. Years worth of important documents, records, photos, etc... could be gone, because the user's finger slipped and pressed CTRL+X, rather than CTRL+C.
Whether or not the operating system should be protecting users in this manner is fully debatable and a matter of opinion, but Apple's approach here is definitely safer (at the cost of being a bit more annoying)
Do you not think that it's terrible UX, to have cmd+x followed by cmd+v for cut and paste in some places and cmd+c followed by option+cmd+v for cut and paste in others?
If you mean cut text and so on, it doesn't match because they're not the same thing. When editing a text document, if you cut some part, it actually goes away. If you saved the document at that point, that selection would be gone.
On files, if you cut a file on Windows for example, nothing happens. Until you paste, no operation is done. So it's not the same thing, and I think the way Finder handles it makes more sense.
Symlinks on the desktop or in Finder to files on network mounts don't receive preview thumbnails. But if you drag that same directory to the dock, those symlinks do receive thumbnails (but only when viewed through the dock.)
