Slashdot Mirror
Mac OS X Power Tools
Here's the thing about book reviews: They're a lot easier to write when you either absolutely hated or absolutely adored the book in question. Once you've decided how you feel about it, it's easy to find a dozen examples of its mediocrity or excellence, as the case may be. However, I've been sitting on this particular review for a few weeks now, unable to finish it because I can't say that I feel very strongly at all about Power Tools. I recently decided, however, that being unable to form a definite opinion of it one way or another is itself a kind of opinion. There's nothing glaringly wrong with it or missing from it, but when it comes down to whether I'd choose to buy it over a different Mac book, I can't say that I would. I realize that this isn't a work of fiction -- its goal isn't exactly to suck me in with thrilling plot twists so that I read the whole thing cover to cover in one sitting. Nevertheless, there are some other books out there that do exactly that (I'll get to them later), and I think I've been spoiled by reading them.
What I Liked
Power Tools covers its bases in a thorough, informative way. It's a solid OS X book, intended for anyone who understands the very basics involved in using a Mac. The author makes very clear early on that he's not intending to show you how to log in, or how to launch an application, but that's about the extent of the proficiency required, I think. Frakes seems to understand his audience and to address it consistently, which is rare enough to be refreshing. One of my pet peeves in technical writing concerns authors who can't decide who they're talking to -- sidebars for beginners and power users are great, but when the body of the text itself waffles back and forth between skill levels, it can be both frustrating and confusing. This is a trap that Power Tools sidesteps completely: At the beginning of each section, you'll find a couple of lines telling you whether an Admin account is required for the techniques described, and whether the changes being made are system-wide or will affect only your own account. Mac OS X Hacks (which is, incidentally and confusingly enough, the Mac equivalent of O'Reilly's classic Unix Power Tools) uses a similar system to introduce each of the hacks in the book, and it's a practice that I'd like to see used more widely.
Favorite sections: Although certainly not the meatiest bits of the book, I thought the quick-reference keyboard shortcut and third-party utility lists were great, and I've used them fairly frequency since Power Tools took up residency on the shelf over my desk. As far as the more substantial content is concerned, I'd have to say Frakes's coverage of Classic is probably one of my favorite chapters -- oddly enough, since I never use Classic myself. That's part of the reason I liked his section on it, though: it does a good job of explaining why you'll want to avoid Classic whenever you can, while also pointing out some ways to make the best of it if it can't be avoided. The list of startup files necessary to use Classic is a good reference for folks who'd like to clean out their old System Folders without crippling anything. And of course Frakes's experience managing and troubleshooting OS 9 comes in useful here -- he points out classics like Conflict Catcher that users shouldn't be without if Classic is used with any degree of regularity.
Chapter 14, covering maintainence and administration of a Mac running OS X, is also full of sound, reasonable advice. Disk care and repair as well as how to recover lost data and prevent such mishaps to begin with are all covered thoroughly and intelligently in this section, as well the whys and wherefores of backups. Nothing surprising, perhaps, but nothing that should be left out of a decent Mac book, either.
What I Didn't Like
Although this is purely a matter of taste and I'm aware that there are many people who disagree with me, I just don't like Frakes's writing style. I have enjoyed some of his columns in the past, but it seems like his humor falls more than a little flat when stretched out over the course of a book. The alliterative titles were amusing for the first one or two chapters, but "Apple-ication Aptitude" is pushing it just a bit, I think. Although I realize that the first priority of a technical book is not to entertain its readers, exactly, is it too much to ask that it enthuse us? I was already interested in OS X before reading Power Tools, but I didn't find anything to excite me -- how would a new Mac user fare?
My least favorite chapter was probably Chapter 6, "Developing a Dynamite Dock." Despite Frakes's promise to assume that the reader is familiar with the basics, there's still the inevitable trot through the relevant Preference panel. Some good third-party software like Tinker Tool is discussed, but there wasn't anything that surprised me in this chapter.
The Bottom Line
This is a perfectly adequate OS X book, and you wouldn't be wasting your money by buying it. Indeed, if you're already a fan of the author, you should probably do exactly that. For me, though, while it does a decent job of accomplishing the tasks it sets for itself, the book just never quite cuts it for me. The bottom line is really that if I had enough money to buy only a single Mac book, this wouldn't be it. I'd spend my forty dollars (or so) instead on either Mac OS X Unleashed or Mac OS X: The Missing Manual. Frakes actually recommends the latter as an alternative for absolute beginners who would be lost in his own book, but don't make the mistake of thinking it's just for novices. It really is a complete OS X manual, covering topics for users at every skill level. As for Unleashed, I've reviewed this book already (more recently than I have the Missing Manual) so I'll just say that if you want a Mac book so complete that it will introduce you to web programming so you can use that default Apache installation, then that's a book you should consider. While I would prefer either one of these books to Power Tools if I were only able to buy one, it's also true that I'm not sorry to have added it to my collection (since, like most people, I'm not limited to one book per subject).
And Furthermore
Dan Frakes is a generally beloved Mac writer and developer and, my ambivalence about this book aside, his stuff is worth looking into. He contributes to the "Mac OS X Secrets" column in Macworld and is also involved in the 9th edition of the Mac Bible. His personal site is danfrakes.com, and the site for this book is at macosxpowertools.com.
You can purchase Mac OS X Power Tools from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
*p_e_n_i_s_b_i_r_d_p_e_n_i_s_b_i_r_d_*
p______...___________________________p
e____(_..__`'-.,--,__________________e
n_____'-._'-.__`\a\\_________________n
i_________'.___.'_(|_________________i
s____________7____||_________________s
b___________/___.'_|_________________b
i__________/_.-'__,J_________________i
r_________/_________\________________r
d________||___/______;_______________d
*________||__|_______|_______________*
p________`\__\_______|__/__''\_______p
e__________'._\______/.-`____{}|_____e
n___________/\_`;_.-'_________/______n
i___________\_;(((____.--'\_/________i
s_________.(((_____.-;\______________s
b____.--'`_____,;`'.'-;\_____________b
i_taco's____.'____'._.'\\____________i
r_dick_--'_________|__\_|____________r
d__________________\_\,_/____________d
*p_e_n_i_s_b_i_r_d_p_e_n_i_s_b_i_r_d_*
Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)Please try to keep posts on topic. Try to reply to other people's comments instead of starting new threads. Read other people's messages before posting your own to avoid simply duplicating what has already been said. Use a clear subject that describes what your message is about. Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
IS a power tool!
At least in my book.
Let's start with the windowing environment, since that is the first thing users will notice. While both KDE and GNOME are mature, stable, and accepted as IEEE standards, Apple has elected to use neither. In fact, they don't even use X at all! Their display system is a proprietary, closed-source system called Quartz Extreme. In addition to the moral issues involved with closed software, this precludes the user from running X apps. There is an untested and alpha-quality X11 emulation layer available for download, but it is emulation, so programs will be slow. Does this sound like a standards-based system to you?
Looking under the hood, it gets worse. While all other *nixes use standard ELF binaries, Darwin (Apple's name for their proprietary "Unix" kernel) does not. It uses Mach-O, an unproven format that is proprietary to Apple. The moribund FreeBSD, off which OS X is based, uses ELF, so clearly Apple went to the extra effort of "switching" (heh) simply to break compatibility. With ELF, users would be able to run most of their Lunix apps; with Mach-O this is impossible. Additionally, Apple has moved most configuration info fromhuman readable text files into a proprietary database called "NetInfo", which is much like the Windows registry we all loathe. Why? These are only a few of the ways that Apple has deliberately broken compatibility with other systems, presumably in order to lock users in to expensive Mac hardware.
When we factor in the threat to users' civil liberties that is posed by the DRM included to support the iTunes Music Store (do you really think it will end there?) it is obvious that real *nix gurus should give OS X a wide berth. Caveat emptor.
My favorite tool to use on a Macintosh is a claw hammer. And then a crowbar. Followed by a reciprocating saw, a nail gun, and then a Colt .45.
Shutting down free speech with violence isn't fighting fascism. It IS fascism!
In addition, during this file transfer, Netscape will not work. And everything else has ground to a halt. Even BBEdit Lite is straining to keep up as I type this.
I won't bore you with the laundry list of other problems that I've encountered while working on various Macs, but suffice it to say there have been many, not the least of which is I've never seen a Mac that has run faster than its Wintel counterpart, despite the Macs' faster chip architecture. My 486/66 with 4 megs of ram runs faster than this 300 mhz machine at times. From a productivity standpoint, I don't get how people can claim that the Macintosh is a superior machine.
Mac addicts, flame me if you'd like, but I'd rather hear some intelligent reasons why anyone would choose to use a Mac over other faster, cheaper, more stable systems.