Skip to content

Apple Universe

Top-level category for all Apple, Mac, and OS X related topics.

RIP Mac OS X Hints, Nov 4 2000 – Nov 4 2014

Note: The following is my unofficial eulogy for Mac OS X Hints; IDG has not announced any plans regarding the site, though I would hope they'll leave it online, even if no new hints appear in the future. The site is now officially in read-only mode; there will be no new hints. So it's officially comatose, at least.

Dearly beloved…

On this, the occasion of its 14th birthday, we're gathered here to mark the passing of Mac OS X Hints.

While it can be hard to tell exactly when a web site has died, the signs are fairly obvious. It's been over 45 days since the last new hint appeared on the site. There is no way for new users to sign up for an account. There's been one new comment posted in the last two days. A sidebar box proudly proclaims Latest Mountain Lion Hints. The site design, logo, and icons were last updated when I worked for Macworld, over four years ago. To paraphrase a Star Trek character, "it's dead, Jim."

To be fair, it's a bit more Monty Python "I'm not dead!" than officially dead, but really, the site is a dead man walking. Now that I'm done with movie analogies, let me explain why the passing of Mac OS X Hints isn't a bad thing. (Note that Mac OS X Hints' passing is in no way a reflection of its management by Macworld. In fact, the opposite is true: I believe the site would have ceased to exist years ago without their involvement.)

The simple truth is that the need for OS X hints has tapered off to near zero over the last 14 years. And that's a good thing.

[continue reading…]



Mac OS X Hints turns 14

Fourteen years ago today, I launched Mac OS X Hints, with this simple post. The Mac OS X 10.0 Public Beta was only a couple months old, and many Mac users (myself included) were feeling lost in the land of Unix and Terminal. (Despite anything Apple said at the time, Terminal was very much a required aspect of using Mac OS X in those early days!)

Related post: RIP Mac OS X Hints, Nov 4 2000 - Nov 4 2014

At the time of launch, I knew nothing about content management systems or PHP; I knew enough HTML to be dangerous, and very little about anything else—including design, as you can see from the image at right.

That image, courtesy of the Internet Archive's Wayback Machine, was taken one month after launch. Could it be any brighter and uglier? Probably not. While I did many things wrong during that launch, I did get a few things right…

  • The site was all about the community; it was my intent from day one that it would be a users helping users site, not a "me telling the world what to do" site.
  • The content management system I chose, Geeklog, has proven to be very long lived—fourteen years on, and it's still what powers the site. In all that time, we had (I believe) exactly one hacking incident. Not bad.
  • The site had a laser focus on hints; I'd do a pick of the week, but outside of that, it was all about the hints.

So despite my poor design and lack of PHP skills, the site flourished. So much so that Macworld purchased the site and hired me in June of 2005. I spent nearly five years with Macworld, before leaving in 2010 to join Many Tricks.

In looking back, never in my wildest dreams did I imagine the site would flourish to the point where it would actually change my career. But it did, and for that, I'm eternally thankful to everyone who helped make macosxhints.com what it was. So happy birthday, Mac OS X Hints!



Migrating away from FireWire hard drives

If there's one downside to my new Retina iMac, it's that it completely lacks FireWire ports. While my main data storage is a Thunderbolt RAID array, all my backups (Time Machine, offsite drive, boot drive clone, and extra paranoid backups) are done on FireWire drives.

My setup precludes using Apple's Thunderbolt to FireWire adapter. (Because I use two external non-Thunderbolt displays, they end any sort of chaining capabilities. With some rewiring and an expensive Thunderbolt dock, I can sort of work around that problem—but those docks are pricey.)

The money-is-no-object solution is, obviously, to replace all the FireWire drives with Thunderbolt drives. Given I drained the computing budget to purchase the Retina iMac, that's not going to happen any time soon. ($400 for a 4TB drive, and I'd need three of them plus a smaller drive for the boot clone.)

After some digging, I managed to convert from FireWire without buying new hard drives, and spent just over $100 in total. The solution? The more-than-fast-enough USB3 bus in the new iMac.

[continue reading…]



Yosemite: An alternative zoom-to-fit action

As you're probably aware, Apple changed the functionality of a green button click in Yosemite: it not longer "zooms to fit" (which could have different behaviors per app), but instead it enters Full Screen mode (if the app has one; otherwise, it does zoom to fit). If you want zoom-to-click, you can option-click the green button; there's no apparent way to toggle these two functionalities.

But today, I discovered a second zoom-to-fit shortcut: double-click the window's title bar. This is easier to do, as you don't have to hit the small green button target; just get the mouse anywhere in the title bar, and double-click.

Note that this won't work if you have "Double-click a window's title bar to minimize" enabled in the Dock System Preferences panel.



A very quick look at the Retina iMac’s graphics performance

While I'm still busy setting up my Retina iMac—given I always do this by hand, it's time consuming—I did take a few minutes to see how the graphics performance compares to that of my mid-2011 iMac.

To test the Macs, I use a visual benchmark called Unigine Valley. This benchmark puts the graphics card through a real workout, and is fun to watch while running. Before the results, here's a quick comparison of my two iMacs:

2011 iMac2014 iMac
CPU3.4GHz Core i74.0GHz Core i7
RAM16GB24GB
GraphicsAMD HD 6970MAMD R9 M295X
VRAM2GB4GB

And here's how they did…

2011 iMac

2014 iMac

I'm no math whiz, but it looks like the new Retina iMac is over twice as fast in the graphics realm as my older machine. I knew it'd be faster, of course, but I wasn't expecting that kind of speed up. Wow.



Quick poll: How many iDevices do you own?

From fiscal 2002 (the iPod's launch year) through fiscal 2014, Apple sold 1,224,700,000 iPods, iPhones, and iPads. That's a lot of iDevices! In looking around our (four person) home, I count more than I would have expected. So that got me thinking, how many of these things do other people own?

Hence this simple poll. It doesn't matter if the device is in use or not in use, working or not working…I just think it might be interesting to see how many of these things each of us owns.

Voting is 100% anonymous; I'm not collecting or tracking IP addresses or any other identifiable information. So take a second and tell the world how many iDevices you own.



Yosemite: Tweaking Safari’s URL bar settings

Safari in Yosemite is a familiar yet new beast. Among the interface changes, I really didn't like the way the URL bar behaved. In particular, these things bugged me:

  1. Not being able to see the full URL.
  2. The width of the URL entry box.
  3. The drop-down that appears when you click in the URL bar (when you have a page loaded).

Thankfully, the fixes for these three issues are easy, if not completely obvious.

Full URL not visible in URL bar

By default, Safari truncates URL to just the base "dot" address, regardless of where you are on a site. So if you're reading my hint about using a dark Dock, Safari's URL bar will display this:

https://robservatory.com

But you're really on this page:

https://robservatory.com/yosemite-dark-dock-and-app-switcher-with-light-menu-bar/

If you prefer knowing where you are in the site hierarchy at all times, the fix is simple. Open Safari's Preferences, go to Advanced, and add a checkmark next to "Show full website address."

The URL box will now show the full URL of the page you're viewing. Of course, that will lead to a second problem—the URL box isn't large enough to display much of the extended URL. Thankfully, that too is an easy fix.

[continue reading…]



Yosemite: Dark Dock and App Switcher with light menu bar

High Sierra update: This trick no longer works in High Sierra. As far as I know, there is no workaround.

Here's my first (only?) Yosemite hint, courtesy of my Many Tricks partner, Peter Maurer. Peter wanted a light menu bar, but preferred the contrast given to application icons in the dark Dock—like this:

Here's how to achieve that effect.

  1. Open Terminal, then copy/paste this and press Return: defaults write NSGlobalDomain AppleInterfaceStyle Dark
  2. Paste or type killall Dock and press Return. The Dock will relaunch in its dark mode.
  3. Copy/paste this and press Return: defaults remove NSGlobalDomain AppleInterfaceStyle

The first step sets dark mode, step two restarts the Dock to switch it to dark mode, and step three turns off dark mode—but the Dock won't notice, and will remain in its dark state (until it's next restarted, which isn't often). Because the Command-Tab switcher is associated with the Dock, it will also be dark.

If you're going to script this, you'll want to insert a delay between the second and third steps, so that the Dock can finish launching before you disable dark mode. Neat trick!



How I configured my 5K TV with bundled computer

After seeing the new iMac with Retina 5K display (I'm just going to call it a Retina iMac from here on out, or even riMac for short), I decided it was time to upgrade my aging but still oh-so-functional mid-2011 27" iMac.

For those contemplating the same upgrade, you may be mulling decisions on processor, RAM, storage, and graphics cards; here's the logic behind each of my choices in those areas, in case it helps you with your decision.

CPU

This was the simplest decision to make—I always buy the most powerful CPU I can afford. In the case where the choice is a Core i5 vs. Core i7, I will always go for the Core i7. That's because only the Core i7 supports hyper threading, which, as Apple writes, is "a technology that allows two threads to run simultaneously on each core. So a quad-core iMac has eight virtual cores, all of which are recognized by OS X. This enables the processor to deliver faster performance by spreading tasks more evenly across a greater number of cores."

In addition, by upgrading the CPU, I make the machine more usable many years down the road—whether for my own use, or when reselling to someone else.

[continue reading…]



Goodbye cron task, hello launchd agent

On April 29th, 2005, Apple launched Mac OS X 10.4, aka Tiger. With Tiger came launchd, a new Unix-side job scheduling tool. launchd was intended to replace cron, the long-established (and quite cryptic) tool for such tasks.

And now, a mere nine-plus years later, I decided it was time to give up cron and move to launchd myself. Mr. Bleeding Edge, that's me! (Note: Unless you enjoy the Unix side of OS X and currently use cron to schedule tasks, this article won't be of much interest to you.)

Why now, after so long as a holdout? Primarily because I kept running into issues with cron tasks that needed to do things as "authorized me," such as mounting an encrypted disk image, or even just mounting a network share. Or my Mac would be asleep for a scheduled cron task, and it therefore wouldn't run. (launchd will queue any missed tasks to execute when the Mac reawakens.) Finally, my cron file was getting huge and unwieldy, and making simple changes was fraught with danger of breaking something.

So I dedicated a portion of a recent weekend to figuring out launchd, and migrating my cron tasks to this brave no-longer-at-all-new world. If you're still hanging on to cron, read on to see what I've learned about launchd—maybe it'll inspire you to move, too (or not).

[continue reading…]