3 ms·
Well, what else would you put on the context menu for a volume? And it's more common then that - pull the plug on a device without ejecting it first, and you'll
by ars 18y ago
Well, what else would you put on the context menu for a volume? And it's more common then that - pull the plug on a device without ejecting it first, and you'll want to check it.
There's more stuff that just doesn't work well for me, those two just happened to be things that I noticed earlier.
Here's another: I put my USB flash disk in, and it read and read and read (it worked fine yesterday). I have no idea where I would find status info on what it's doing.
On linux it's easy: dmesg. (Ok, not obvious, but easy.) On windows it at least makes an icon immediately, and then reads it. On the mac? No clue. There was no indication it even noticed it except the light on it flashed constantly.
Mac's just don't think like me. I fight with the interface whenever I use it. It tries to hide the internals of the computer to make it easier to use. But for me that doesn't work - I understand the computer and I want to see what's it's actually doing, not the sanitized version.
Another example: in list view if you double click on a name it tries to rename it. You have to click on the picture. But I don't like that - if I want to rename, I'll use the menu and pick it (or make it be triple click). But they can't do that - it has to be easy for people to figure out how to rename, but at the expense of being able to launch something by clicking on the name.
Even if I would get used to a mac I'd find zero benefits. I don't need easy to use, I need discoverability and verbosity. Give me every single option, and lots of text.
- demallien 18y agoWhat else? Well, Open, Eject, Get Information, Copy, Rename and Format are things which I'm guessing get done more often than running a disk check, and hence may be more suitable as options on a contextual menu. The Mac almost certainly has a command line tool that is the equivalent of dmesg (I don't know for sure, as I've never had any need, as I just use the graphical interface provided in Disk Utilities, but I'd be astounded if this wasn't the case. How is this done in BSD land?). As for double clicking on the name in list, normally this launches the file (I've just checked on my Mac). If your system decides that you are trying to rename the file instead, there are two possibilities - you've moved the mouse between clicks, or you're clicking too slow for whatever the setting for double clicks is in mouse preferences. Even if I would get used to a mac I'd find zero benefits. I don't need easy to use, I need discoverability and verbosity. Give me every single option, and lots of text. Well, you're a tiny tiny minority that Apple just doesn't care about. Most people don't want verbosity, it annoys them. They don't want lots of options that they don't understand, it stresses them out. Outside of this majority are the power users, who can write scripts and apps to fill in any blanks on their system that they feel that Apple has missed. And then there are people like you - people that know another system, and think that the Mac should act just like it. That will never happen. All of those options that you know from the Linux/Windows world confuse the majority of users. Apple understands this, which is why their market share has been going through the roof in recent years. If you miss them, you have two choices: become a Mac power user (if you know Linux, it won't be such a stretch, all your fave tools are there, from ipconfig and tcpdump, through to bash, perl, ruby and python), or accept that the Mac is not for you, and can never be for you without Apple comprising their main market.