Confessions of a Mac Junkie: Word Processors

A long time ago (late 1980s) the best word processor for the Mac was Microsoft Word version 4.0, no contest. Basically, it was that or vanilla MacWrite. Word was much smaller then, more lightweight. Edges of the bloat could be seen with version 5, and version 6 was one of the most colossal disasters in office software history. I’ve also owned Write Now, MacWrite II, MacWrite Pro, various flavors of Nisus Writer, WordPerfect Mac, ClarisWorks/AppleWorks, FrameMaker, Mariner Write, Pages, and I’ve taken several others for test drives (Mellel, a few others whose names I can’t remember). There is a clear winner in terms of history for the best word processor for the Mac, ever. In my opinion, MacWrite Pro was, hands down, the king. Things printed where you put them. Style sheets always made sense and worked in sensible, predicable ways, and there was a differentiation between character styles and paragraph styles that promoted a mental model of the system that actually worked. It had just enough page-layout-style features that you could control things, but it never overwhelmed you with that stuff.


But, unfortunately, MacWrite Pro is dead. The last version released was a long time ago, and once development stopped, it didn’t last long, mostly because it had issues with newer printer drivers, and if you can’t print properly from your word processor, it’s done.

Now, because I’ve tried so many, I now have a standard test I do when I take any new word processor for a spin. Before I get into that, though, I think it’s important to mention what kind of writing I typically do with word processors, because what works for me might not work for other people depending on what kind of writing you do.

I’m an academic, but I don’t write books. I write scientific journal articles, conference papers, book chapters, and grant proposals send to federal agencies. I also write exams and homework assignments and answer keys for those. I write almost no memos or letters; that’s what email is for in my world. I don’t write fiction, advertisements, brochures, forms, or anything like that. I don’t use my word processor as an outliner; I have an outliner for that. (Yes, there will be a series entry on outliners.) So, my primary use is technical writing.

So, what’s my fist test? I try to generate a document in what I think of as “conference proceedings format.” This is pretty straightforward two-column format, which virtually all word processors can handle with very little pain. The tricky bit is that the first page is different; it requires a single-column start with the paper tile, author information, and sometimes abstract. I also need style sheets to handle various heading levels, figure captions, and body text that sometimes does and does not require a first-line indent depending on whether or not it follows a heading. Maybe this doesn’t sound complicated and it definitely should not be hard for someone with a graduate degree in computer science to figure out.

Most word processors, however, make this task way, way more difficult than it should be. I can usually get most word processors to do it, more or less, but the issue isn’t usually whether or not they can, but how much of a pain in the ass it is to get it running and how sensible the outcome is in terms of mapping from what it shows on the screen to what gets printed on the page. I dislike most implementations that require “sections” to do this. Doing it with a header that appears only on the first page is OK, but doing it with a WYSIWYG text box is the clearest and easiest way I’ve seen to handle this. This is, of course, how MacWrite Pro handled this.

When MacWrite Pro was no longer feasible to run, then I switched to FrameMaker for a while, but that never made the OS X transition, so that wasn’t a viable option. I had been floating around trying different things, none of them quite what I wanted. Mariner Write is non-awful and Nisus Writer Pro has some things going for it, but neither is quite it.

A word, then, on Microsoft Word. I hate Word with a passion. It’s slow (NASA launches things faster), it’s bloated with zillions of features that I will never, ever use, the UI is klunky (exactly how many modal dialog boxes are there?), the implementation of style sheets is horrible, its behavior is completely unpredictable (gee, I wonder where that figure will actually end up, or how it will reformat my text if I somehow accidentally delete the invisible formatting character), and so on. It’s a mess. I only use it when I absolutely have to, generally because I’m working with a colleague who uses it. Even then, I’ll generally translate from Word, edit in something else, and then save back to Word. This is not to say everything about Word is bad, as Word has been the source of some very good ideas. For instance, the first time I saw the dynamic red underlining of misspelled words was in Word, and even if Word didn’t invent that, it popularized it, and that’s a seriously good bit of UI.

So, what I use is Apple’s Pages. It’s the closest thing to MacWrite Pro out there, it’ll always run on the latest Apple hardware and software, it plays surprisingly well with Word, and the UI doesn’t suck. It’s certainly not because it’s an Apple product; I have to say that the first couple of versions of Pages weren’t especially great, and I didn’t really use it. However, the 3.0 (or ‘08) version (actually released in 2007) was good and the 4.0 (or ‘09) version is a useful improvement over that. When people email me Word documents, I almost always open them in Pages because it takes dramatically less time to launch Word and Pages usually does an excellent job of importing with formatting intact. And as much as I dislike “track changes,” Pages does a good job with it and generally handles Word files that have this turned on quite well.

However, it’s not perfect. For example, MacWrite Pro’s style sheets were still better, and it’d be nice if Pages did auto-numbering of figures and equations, but other than that, it’s good enough that I almost don’t miss MacWrite Pro anymore, which is an accomplishment. So, that’s what I use. For now, until someone finds something better.

3 thoughts on “Confessions of a Mac Junkie: Word Processors”

  1. Did you ever find a convenient way of automatically dropping a first line paragraph indent right after a heading in Apple Pages 3.0/4.0?

  2. It’s not great, but it’s not too bad. You have to define two “body” styles. The heading style is then followed by the body style with the different indent, and that style is then followed by the “normal” body style, which is followed by itself. (You set these up with the “following paragraph style” in the “More” tab of the Text palette—no, not the easiest thing to find). It’s a little klunky but it works OK.

  3. I also miss MacWrite Pro. I think that v4.5 was the last program that I really felt like I had any mastery of.

    It did everything a word processor needed to do. It didn’t do everything that a word processor does, today. But it did everything that a word processor needed to do. I think by the time you can watch television on your word processor, you have pretty much added all of the features that anyone is ever going to require, whether or not they are even aware of those features or understand how to invoke them.

    I tried for years to like WriteNow. I was most happy with v2.2, the one in the maroon-and-white box. The people were nice at the various Macworld Expos and I may be misremembering it, but there were stories that the woman who sat in the Big Chair was dating Bill Gates around that time.

    I monkeyed around with Nisus after Steven Levy told me that you could configure it to be and to do practically anything. But it turns out that I wasn’t that clever and when I needed to get pages done I always returned to MacWrite Pro v4.5.

    Today, I also lean on Pages, unless I absolutely have to work and play well with someone using Office. Then it’s back to Word, again.

Leave a Reply

Your email address will not be published. Required fields are marked *