A terrible article about word processing

So, this eleven-year-old rant against Word 97 is making the rounds again for some reason.

What a giant piece of Linux-nerd garbage!

Apparently, the author and his fans believe that:

  1. Only “professional typesetters” should dare to get close to such dangerous choices as “font size.” The unwashed masses might cause some sort of nuclear meltdown if allowed to decide on the appearances of their documents.

  2. Unless you bother to learn a markup language for displaying mathematical formulae that, unless you are a publishing academic mathematician or scientist, you will never, ever have occasion to use, you should not be allowed to use any text ouptut format besides ASCII.

  3. Issues from a version of Word released in 1997 that have since been corrected, such as lack of free backwards compatibility, are somehow still worth raising.

  4. It’s OK to waste everyone’s time by making them read a poorly thought out rant against the existence of the subhuman class known as “people who do not work in computer science professionally” and then spill, at the end, that this actually isn’t about the ease of use of a program at all, but is another ideological anti-Microsoft rant from doctrinaire open-source zealots who are angry at something being successful.

Shame on anyone who pollutes my inbox with this nonsense. Go play with your hacky-sack, hippie.

“Word processors do to words what food processors do to food.”

7 bit or 8 bit? because I’ve actually had occasion to to use the special characters above 0X80.

You don’t really need to read past the second line, where the author spells his own name wrong. Fool.

ETA: Then very quickly you discover the author doesn’t know how to use “quotes,” either, so you can just disregard everything he’s “saying.”

I suspect that the article predates the wide adoption of Unicode. The idea of people using a word processor like Word to create documents in Chinese or Japanese would probably blow the author’s few brain cells.

The worst thing about Linux is the people who proselytize for it.

Not so different from any other religion.

Huh. I’d say the same about Apple zealots.

But I’d most assuredly not say that about Windows, for there is much that is far, far worse in Windows-land. :smiley:

I don’t think you have that much to worry about from the guy’s One-man Campaign For The Destruction of WYSIWYG. Judging from his homepage, he’s a hobbyist TeX freak. TeX people tend to fall in love with their Chosen Tool and consider using anything else as blasphemous. I’d just shrug and move on if I were you.

The funny thing is that the term “Linux-nerd” is as ancient and outdated as the TeX guy’s rant. Linux has broken through to the server and embedded systems markets ages ago, and is considered a mainstream operating system. In fact, it’s extremely likely that The SDMB runs on a Linux machine, given that it uses the vBulletin software, written in PHP. The days of “pocket protector-adorned neckbeards” fighting holy war to get recognition for a niche OS are long over.

Of course, every operating system has people that love it Far Too Much

Condescension and rational critique apparently don’t go well together. To respond to your points in order:

  1. Only “professional typesetters” should dare to get close to such dangerous choices as “font size.”

That’s not even close to what he said; what he said, after acknowledging the need for people to do their own typesetting these days, is that the WYSIWYG word processing model encourages people to fuck around with fonts and type size and other formatting when they should be concentrating on content.

  1. Unless you bother to learn a markup language for displaying mathematical formulae that, unless you are a publishing academic mathematician or scientist, you will never, ever have occasion to use, you should not be allowed to use any text ouptut format besides ASCII.

Again, not even close to what he said. What he said is that ASCII is better for composing and transmitting digital text, being portable, compact, and less prone to corruption than, say, .doc files.

  1. Issues from a version of Word released in 1997 that have since been corrected, such as lack of free backwards compatibility, are somehow still worth raising.

As you said, it’s an 11-year-old article. Besides, switching versions of Word still fucks up formatting, and since Word 2007, .docx files have been a pain in the ass for users of earlier versions.

  1. It’s OK to waste everyone’s time by making them read a poorly thought out rant against the existence of the subhuman class known as “people who do not work in computer science professionally” and then spill, at the end, that this actually isn’t about the ease of use of a program at all, but is another ideological anti-Microsoft rant from doctrinaire open-source zealots who are angry at something being successful.

Don’t know where you got this; Cottrell, while acknowledging his bias, clearly feels that Word isn’t good at what it does, but is succeeding despite its faults because of Microsoft’s market power. And Cottrell isn’t in computer science, he’s an economics professor, albeit a major geek.

I don’t agree with him about all this; I think that Word sucks for entirely different reasons. A two-step process of writing and formatting is perfectly feasible in WYSIYG; although Word does make this difficult with its automated style-based formatting, it can be set up for plain text entry, and I refuse to believe that marking up with TeX is easier than doing it with Word styles.

Nonetheless, I do agree with his main point: Word, regardless of its virtues, does not serve well in providing a standard text format, and it’s entirely due to Microsoft’s leverage with Windows that it has been adopted as such. If you need to transmit text alone, plain text is better. If you need to transmit formatting, an immutable format like PDF is better. When transmitting my résumé to a potential employer, for example, I am usually required to send it as a .doc file. I have a meticulously formatted résumé, and it’s usually fucked up by the version of Word on the receiving end. If they’d let me upload a PDF, they’d see it as it’s meant to be seen.

Also, I’d rather use WordPerfect. But that’s another thing entirely.

Moved from The BBQ Pit to Mundane Pointless Stuff I Must Share.

Gfactor
Pit Moderator

For what it’s worth, I found Word somewhat intimidating- my first impression was “more buttons than the control panel on the Space Shuttle”. I had to invest in a Word for Dummies book to get really comfortable with it. It is extremely versitile, but probably 95%+ of what I type could be handled by WordPad (you know, that program buried in Programs/Acessories?). There are features of Word I’ve never used, such as automatic Styling of headings, etc. and other features that are counter-intuitive enough (page numbering is part of Headings and Footings?) that since I don’t use them frequently I find myself refreshing my memory from the Help feature when I do need them.

I’m just old enough to have used a non-WYSIWYG word processor. I’d rather have every hair on my body individually ripped out by a rabid aardvark than use one again.

Wait, are they saying that something like the blue screen and having to know what all the function keys are WordPerfect was the ideal in word-processing? Cause if they’re saying that, they’re stupid. Put me in line for the rabid aardvark.

Reminds me of Roy Blount, Jr., writing in 1985, when a WP was hardware, not software…

Source

“Heading” != “header”.

A heading is the visually distinctive text used to demarcate sections of your document.

A header is the text at the very top of a page that often contains information such as page numbers, author names, and the like. A “footer” is the similar text at the bottom of a page.

When I had to write my master’s thesis there were a ton of rules about formatting, all of which the author had to take care of. I did it all in Word, but I did wonder from time to time if it would have been easier in LaTex. Now, this was chemistry and not physics or math, so while I had to embed a lot of graphics they were all coming out of ChemDraw and I wasn’t putting in mathematical formulas where something like LaTex excels.

Organic Letters is kind of the same way. They give you a template and you must fit everything in the template. I’ve known people who wrote an article for Organic Letters that spent more time fighting the formatting than they did writing the actual article. It makes me wonder what the editor actually does.

I’m not sure you read the article very carefully. Like Nametag said, you pretty much missed his point entirely.

And fundamentally, his point is a very good one, and one that is every bit as valid today as it was in 1999: conflating the process of content creation with the process of typesetting is an ineffective way to get work done. It makes future maintenance far more difficult than it has to be, it can give inconsistent results, and while the typesetting is distracting you from the important business of writing a structured and coherent document, the writing is distracting you from the important business of creating an effective and attractive presentation.

Now, obviously it would be silly to suggest that tools like MS Word are bad for everything. There are cases where pure WYSIWYG editing may indeed save you time – for example, if you’re just whipping up a poster for a neighborhood bake sale that’s happening tomorrow and that you just learned of five minutes ago, or something else of the sort. Quality is not really important and you know you will never have to maintain this document, so taking three minutes to fling it from fingers to word processor to printer is an efficient way to accomplish your goal.

Modern word processors have, of course, become much better at enabling the effective separation of the writing and typesetting tasks. Unfortunately, almost nobody uses these capabilities, because barfing both content and form out at once with WYSIWYG is far too easy. And it does seem easier at first, so why not, right? The problem is that for anything much more serious, complex, or needful of future maintenance than a bake sale flier, WYSIWYG editing is seriously counterproductive. In that case, doing it properly (whether you’re using a text editor and LaTeX or making appropriate use of MS Word’s styles) will make your job easier and save you time in the long run.

Make it delicious?

Turn a steak into shit on a shingle.

According to Netcraft it’s FreeBSD.