There’s a derogatory term used on discussion forums for people who blindly support an operating system and poo-poo its shortcomings and weaknesses, despite all reasonable evidence to the contrary: Fanboy.
I’m no Apple fanboy. Yes, it’s my operating system of choice, and I recommend it to people whenever I can, but that doesn’t mean there aren’t things about it that make me nuts. Now, I’m in “corporate IT guy mode” at the time of this writing, so I’m setting aside all the great things the Mac can do as a creative tool and focusing on the work-a-day aspects of it.
First-up: remote control. Quite frankly, Apple’s Remote Desktop feature is lame in many ways when compared to Microsoft’s remote desktop solution (based on the very mature and solid Terminal Services foundation). Apple RD is slow, allowing minimal customization of the remote view upon launch. You get a color slider, and that’s about it. Any adjustments you want to make to the remote GUI have to be done within the remote GUI. That’s absurd – why should I have to suffer through all those remote clicks and make trips to System Preferences? With a Microsoft RDC client, I can create a remote connection profile that specifies screen resolution, color depth, sound on/off, mapping local to remote drives, mapping printers, and more before I even connect. And the speed. Yikes. Microsoft’s RDC performs so well, sometimes I forget that I’m not actually at the computer I’m controlling.
Now, in fairness to Apple RD, it does do some things that Windows RDC doesn’t do. You can generate a variety of reports on remote systems, send application packages that automatically install software and reboot the remote system, and observe a remote desktop versus controlling it. I just wish they’d fix the speed issue. It could be that part of that speed issue has to do with the Mac GUI itself. For example, there’s no way in OS X to turn off the fat, obnoxious drop shadows behind every window. Those drop shadows make remote control sessions slower, because the remote session has to draw that many more pixels.
Second – badly behaving network shares. Maybe this one should be first. Connect to a share on your network so that the remote volume mounts on your desktop. “Family Room iMac” for example. Fine. Now, go shut down Family Room iMac, return to your computer, and you’ve got about an 80-90% chance of staring at the bouncing beach ball for 2 minutes the first time you open a Finder window or click on the desktop (tip: force-quit the Finder to get out of this situation). Even if you don’t try to access that now-closed share. That’s ridiculous for an operating system with Unix underpinnings. Windows doesn’t do that. A Windows share does nothing at all until you double-click on its icon. And then, Windows just says “nope, that share’s not here” and lets you go about your business.
You can imagine how this little problem becomes a big problem in an office environment with 20 or more Macs connecting to each other, off and on all day. Invariably, somebody you’re connected to via sharing shuts down and goes home for the day whilst you’re still working. Grrrr.
Third – Apple really needs to fix the shortcomings of the Finder. There’s even a phrase that’s been coined for this desire: “FTFF.” You can figure out what the abbreviation stands for, ha ha.
Sometimes when I have to spend all day working on a Windows system, I realize just how much better of a workhorse Windows Explorer can be. The Finder just has too many maddening little quirks that surface after hours and hours of heavy lifting.
For example, one thing I can’t stand is that if select a bunch of files from one folder, and drag to copy to another drive or folder, and one of those files can’t be copied for some reason (it’s corrupt, or has a bad filename, whatever) THE WHOLE OPERATION TANKS. On Windows, you’ll get an alert about each and every file that can’t be copied, and you can decide to continue the operation with the rest of the files or cancel.
There are tons of other Finder “issues” – so many, that there’s a software company out there who’s main product, "Pathfinder,” is meant as a Finder substitute. I’ve purchased and used Pathfinder in the past, and always end up disabling it after a few months because of its system overhead and quirkiness. But I see that they’ve got a brand-new version out, so maybe I’ll give it another shot. I do miss its tabbed Finder windows and ability to customize all text and icons with OSX.
And finally, peer to peer file sharing on a network, with trusted computers set up with shares which everybody should be able to read and write to, is NOT as simple as it should be. In fact, it’s downright maddening. In this case, Apple technology does NOT “just work.” It’s not the Apple way. It’s more like the “obscure Linux way” or something. I’m sorry, but Windows NTFS settings for permissions and file shares are much, much easier for me to work with.
I can imagine how somebody with less experience might go mad trying to sort out peer-to-peer sharing. I have issues on my company’s network with shared folders that I’ve never, ever been able to figure out, and believe me I’ve tried. Sometimes they work for one user, but not for another with the exact same setup. Sometimes you have to authenticate when you want to put a file into a Mac share that’s explicitly set to be wide-open. Other times, you have to enter a password to copy, move, or even open files ON YOUR OWN HARD DRIVE if somebody else put them there via file sharing.
How about you? Where do you think Apple could make improvements to its operating system – whether compared to Windows or not?
No comments:
Post a Comment