Slanted Viewpoint

I bought my first Macintosh thirty years ago this month, within days of the original Mac going on sale. It was my first personal computer purchase. I had used Apple II’s and even Atari’s where I worked, but I had never owned a computer. Until January 1984.

I had been deliberating for several months prior to January, trying to decide what computer to get. Should it be an Apple IIe, an IBM PC, or this Macintosh thing that was coming? I decided to wait and check out the Mac. I was glad I did. After playing with one at a computer store for all of about two minutes, I was sold. I bought a Mac that day.

The only mystery to me at the time was why everyone in the market for a personal computer did not instantly come to the same conclusion. Why didn’t IBM and Microsoft simply go out of business by the end of the year? For me, the comparison was as if you were back in the days of the earliest mobile phones (the ones that were about the size of a shoebox, which were coincidentally the models available around 1984) and suddenly a company came out with the equivalent of a fully functional iPhone 5S — and the reaction of most consumers was something like “Eh! That iPhone is just a toy. You can’t make real phone calls with it. I’ll stick with my Motorola DynaTAC.”

Yes, the original Mac was that much of a leap forward. Unless you were there back in 1984, it’s hard to imagine how startlingly radical it all was. Heck, I was there and it’s still hard for me to imagine. The Mac featured a graphical display navigated by a mouse; it had an intuitive Finder desktop metaphor, WYSIWYG fonts and the ability to create pictures with the likes of MacPaint. No other computer had anything close to this (except perhaps for Apple’s own Lisa computer, which cost 4X as much). The rest of the bunch were all still stuck using a command line.

The rational part of my brain understood that the original Mac had significant limitations. With only 128K of memory, a single floppy drive and virtually no application software, it clearly wasn’t ready to replace existing PCs. But the emotional part of me would have none of that. At the very least, you had to be rooting for the Mac to succeed, even if you weren’t ready to buy one. Or so I thought.

As you likely know, my expectations did not translate into reality. Many people were not rooting for the Mac. At least not at first. The Mac did not become an overnight blockbuster — despite generally rave reviews. Numerous obstacles, some quite huge, blocked Apple’s (and Mac’s) path to a successful future.

But the story has a happy ending. Apple’s vision for the Mac — and my initial reaction to it — were eventually vindicated. Within less than a decade, with Microsoft “translating” the Mac OS into its Windows software, every personal computer in existence was using a mouse and a Mac-like graphical user interface. Apple had won the war, even if they almost died in doing so.

But Apple didn’t die. Further, not one of the companies that was making personal computers back in 1984 is still in the business of doing so today. Not one of the original computer model names is still in use. Except for Apple and the Mac.

It may not be a tactful, socially correct thing to do, but I can’t resist a bit of gloating here on Apple’s behalf. To all those who laughed at the Mac back in 1984: the last laugh’s on you. The Mac has survived, continues to thrive, and stands alone. Apple itself has become the biggest company on earth!

That’s certainly something worth celebrating. So Happy Anniversary, Mac! Congratulations. Well done. It’s been a fantastic 30 years.

On personal note, as is true of many others, I owe my career to Apple. Without the tools that the Mac provided and the culture that surrounded the Mac, I would not be where I am today. Thank you, Apple.

And now…let the next thirty years of Mac begin…

[For Apple’s take on the Mac’s 30th anniversary, including a look back at highlights from the past three decades, check out Apple’s website.]

I’d like to set the record straight regarding my recent Bugs & Fixes article for Macworld — the one on problems opening PDF files in the latest version of Safari when the Adobe Reader plug-in is installed. To put it as kindly as possible, I could have done a better job on this one.

In a nutshell, the problem cited in the article is that, after installing Adobe Reader, you get continually warned by Safari every time you try to a load a PDF file—requiring a couple of clicks before the PDF will load. I found this so annoying that I decided I’d rather bypass any security advantage and eliminate the warnings altogether. I then detailed how I had some trouble figuring out where and how to do this.

I placed the onus of the blame for this on Adobe and its Reader app. In retrospect, I should have placed the lion’s share of the “blame” (if the term is even appropriate here) on Safari itself. And on myself. Adobe was only making use of a new feature in Safari, one that Apple touts as a providing enhanced security for Internet plug-ins. At some level, this was obvious to me: The fix I cited (which I should have recalled without needing to search for it) required going to a Safari Preferences setting (as shown in a figure in the Bugs & Fixes article). Further, the Preferences screen lists numerous plug-ins besides the one for Adobe Reader. This is a clear tip-off that the situation extends beyond the Reader plug-in. Still, partly because of my prior bias against the Reader, as well as because Apple’s own PDF software does not trigger the same warnings and because I had not had any similar problems with any other plug-in, I viewed it as an Adobe failing. Not so.

I compounded my error by adding a comment that said Adobe “could have handled {the matter} much better.” What could Adobe have done to help ameliorate this? Actually, not much. However, I would have suggested two things. First, on the assumption that many Adobe Reader users may not be clear as to what is going on here, the Adobe Reader app (perhaps in its Preferences screens) should have included the pertinent information—bypassing the need to search Adobe’s or Apple’s support sites. Second (although I understand Adobe would be reluctant to do this), Adobe could provide a simple way to disable or uninstall the plug-in altogether (short of manually having to drag the plug-in files out of the /Library/Internet Plug-Ins folder)—for the benefit those who would like to keep Reader around but not use the plug-in (if there is a setting that does this, I couldn’t find it). Still, as I said, this is minor stuff. And to its credit, Adobe Reader’s Preferences>Internet screen does link to a relevant article on how to manually disable the plug-in.

On a related note, my Bugs & Fixes article also raised the question as to what is the difference between the “Allow” and “Always Allow” options in the Safari settings. I found none. This, as it turns out, is explained in an Apple support document. The answer is: when selecting “Always Allow,” “Safari loads and displays the content without prompting, even if the Internet plug-in is blocked by OS X File Quarantine.” With “Allow,” the Quarantine content remains blocked.

Overall, I fell down on the job with this article. More than once. For that, I apologize. Thankfully, it’s quite rare for this to happen. And I’ll do my best to make sure that it never happens again.