Updated and republished for macOS 10.13.3; skip it unless you really really care about all the macOS releases. Originally published on November 14th, 2005.
Below the break is a table showing all major releases of macOS (previously Mac OS X) from the public beta through the latest public version, which is macOS 10.13.3, as of January 23, 2018—the 109th release in total.
Note: Click the ⓘ symbol to read Apple’s release notes for a given update.
Apple has announced that 32-bit apps have a limited future on the Mac: They’ll be fully supported in this fall’s High Sierra release; macOS’ 2018 release (“Really High Sierra”) will “aggressively warn” users about 32-bit apps, and I would assume, they won’t work at all in the 2019 version of macOS (“That Was My Skull!”).
But how do you know which apps on your Mac are 32-bit and which are 64-bit? MacObserver has an article that discusses the easy way, via the System Information app—just look in the Software > Applications section, and you’ll be able to see a list of apps and a 64-bit Yes/No column. But seeing the list is all you can do—you can’t easily save the list for future reference, for instance, nor can you copy/paste the info to another app.
So here’s a geekier solution to generate a list of your 32-bit apps, saved into a text file for easy future reference. Open Terminal, and paste this command:
This does the same thing as the System Information app, but it dumps the data in text form; the greater-than sign redirects the output to a text file named non64bit.txt, saved to your desktop. The grep is used to show only the 32-bit applications (the full line reads 64-Bit (Intel): No), and the -B and -A options are added to capture the lines before and after that line in the output.
This is probably not overly useful to most people, but I wanted a way to capture the list of apps, as I have over 290 32-bit apps on my machine, and it takes a while to run the System Information report each time.
If you have certain System Preferences panels that you access a lot, and you’re a Dock person (as opposed to a ⌘-Space and type person), here’s a little timesaver: You can add any System Preferences panel directly to your Dock. You can’t add it to the left side, as the individual panels aren’t applications. But they are documents, so you can add them to the right side of the dock—just drag and drop from Finder.
You’ll find the System-provided panels in /System/Library/PreferencePanes; third-party panels may appear in either your user’s Library/PreferencePanes folder, or the top-level /Library/PreferencePanes folder. Find the one(s) you’d like in your Dock, then just drag and drop.
You can, of course, keep System Preferences itself in your Dock, and then right-click to see a list of all preference panels. For those panels you access often, though, this method is much quicker.
Note that I am not in any of the target markets for a typical Mac Pro buyer—I don’t crunch huge scientific data sets, I don’t render massive 4K movies, and I’m not compiling huge programs on a daily basis. But I have always been a fan of the Mac Pro for one reason (up until the most recent one, at least): Customization. Having a customizable Mac means it can last longer, as you can make changes to keep up with technology. I have owned both the Motorola and Intel era Mac Pros, and they were truly excellent machines.
One Mac to rule them all
The older Mac Pro (and its predecessors) were—as I recently wrote—wonderful machines, because you, the user, could do so much to them. You could add RAM, of course, but you can do that to most any current Mac.
You could also choose up to four hard drives to put inside the case—no messy cables, no need to worry about a child or pet disconnecting your drive while it’s rendering a movie, etc. If you outgrew them, you could easily replace them. In my Mac Pro, I had an internal Time Machine drive (in addition to the external Time Machine drive.)
Mac OS X 10.7 and earlier: Launch whatever app you want, the OS doesn’t care.
Mac OS X 10.7.5: Gatekeeper appears, but is a benign master, defaulting to allowing apps from anywhere. You can still install and run anything without any intervention from the OS.
Mac OS X 10.8 through 10.11: The benign master is slightly less benign, as the default setting changed (somewhere in that timeframe) to only allowing apps from the Mac App Store and registered developers. You could still disable Gatekeeper completely, though, as the “Anywhere” button was still present. If you didn’t do that and tried to launch an app from outside the store or a non-registered developer, you had to click OK in one dialog box. Still not awful, but you were aware you were working outside the Gatekeeper’s happy zone.
macOS Sierra (10.12): The benign master is now clearly just the master—the “Anywhere” button is gone. (Gatekeeper can still be disabled in Terminal, if you wish: sudo spctl --master-disable.)
And when you try to run an app from an unidentified developer, you really have to jump through some hoops…
The nice thing about the reinstall is that it’s nothing like a reinstall from days of yore—you’re not starting from scratch, so you won’t have to reinstall everything when done. Apple makes this clear on the support page:
You can install macOS over the same version or earlier version, without removing your data. You don’t need to remove or disable the existing system first.
I say this with crossed fingers, but it seems that this reinstallation has potentially solved my Bluetooth issues. For the last two days, I’ve used my Bluetooth headphones without any static issues at all. In addition, none of my Bluetooth devices have disconnected. There is one comment from slajax on the original article that states this didn’t work for them:
I’ve been having the same issue but with the gen 1 track pad and keyboard. I reinstalled the OS, PRAM etc replaced them with the gen 2 key board and track pad and also had the apple store replace the bluetooth antenna but still having the same issue.
If you’ve reached the breaking point with your macOS Sierra/Bluetooth issues, it might be worth the 30 minutes or so a reinstall takes. But please, if you go this route, make sure you have a good backup first, just in case. And if it works for you, please post in the comments (either here or on the original post), so that others might see, too. I promise to do the same if my now-working Bluetooth turns out to again be not-working Bluetooth.
A while back, I wrote about opening Unix man pages in Preview, and this is still my preferred method of browsing man pages. However, there may be times where Preview is overkill, and you want to stay in Terminal, maybe for a short help file such as that for ln. But opening a new window by hand is a bit of a pain, and tabs won’t work because you can’t see both the window and the man page at the same time.
While browsing the old Mac OS X Hints site, I found this nice solution: Open man pages in a new Terminal window, one that’s set up just for reading such pages. It looks something like this (though I’ve customized my setup; keep reading)…
Adding a few lines to your shell’s startup file makes opening these ‘in their own window’ man pages as easy as opening ‘regular’ man pages.
One of the most-useful tools in macOS is also one of the most useless: The Services menu. In theory (and occasionally actually true), the Services menu lets you quickly take action on something—a selected file or folder, or a chunk of text. In reality, the Services menu is a vaste wasteland of unused functionality, and a place where pre-assigned keyboard shortcuts go to hide from your attempts to use them elsewhere.
If you install a fair number of apps on your Mac, you may be surprised by the amount of stuff in your Services menu. Here’s a look at my iMac, after I reset the Services panel (System Preferences → Keyboard → Shortcuts → Services) to its defaults:
If you’re good at counting, you spotted 123 separate services flowing past. Not all are active, of course—”only” 58 are. Of those 58, you’ll see some subset based on whatever you’ve selected…but even that subset can present itself as a huge list:
That’s really not very helpful when you want to quickly apply some action to your selection. To make the Services menu useful again—and to potentially free up some keyboard shortcuts—you’ll need to actively manage your Services.
However, on my iMac and rMBP running macOS 10.12.3—and on others’ Macs, as my report was based on similarfindings by Michael Tsai and Kirk McElhearn—the Option key no longer worked; it was the Shift key. But on a third Mac here, running the 10.12.4 beta, the shortcut was back to the Option key.
To further add to the confusion, a comment on the original article—as well as replies to the others’ tweets—states that the user’s Mac is still using the Option key in 10.12.3. So I thought I’d create a new user account, and see if I could figure out what was going on.
After some experimentation, I was able to discover why the shortcut key changes, and how to change it between Shift and Option at any time. This clearly isn’t a feature, so I guess it’s a bug, but it’s a weird bug.
Update: See this article for the cause of the shortcut key change. It’s a bug, not a feature…I think.
Via Michael Tsai and Kirk McElhearn, today I learned that I’ve been giving bad advice to our users ever since macOS Sierra 10.12.3 shipped.
It used to be that holding Option in Finder and then clicking the Go menu would reveal an entry for the normally-hidden Library folder. In macOS 10.12.3, for reasons unknown, Apple has changed this: The only thing the Option key does now is change Go > Enclosing Folder into Go > Enclosing Folder in New Window. To see the Library folder entry, hold down the Shift key instead.
So that’s the bad news: They changed an undocumented shortcut that many users have been told to use when troubleshooting. The good news is they added a better, easier, and faster way to get to the Library folder: Just press ⇧⌘L in Finder. This matches all the other shortcuts—⇧⌘O for Documents, ⇧⌘D for Desktop, etc. (Downloads is the odd one out, as it uses ⌘⌥L.)
Note: This may be a short-lived change, perhaps even a bug—it seems to be gone in the 10.12.4 beta release. Either that, or the 10.12.4 build is a bug, and it’s supposed to be how it is now in 10.12.3. Hey Apple, I have some advice on how to fix this whole messy situation: Stop hiding the Library folder by default! (Note that you can unhide it by showing View Options (⌘J) on your home folder and checking Show Library Folder.)