Charlie Stross: Why Microsoft Word Must Die
Jeremiah Cornelius writes "Rapture of the Nerds co-author Charlie Stross hates Microsoft Word, worse than you do. Best of all, he can articulate the many structural faults of Word that make his loathing both understandable and contagious. 'Steve Jobs approached Bill Gates... to organize the first true WYSIWYG word processor for a personal computer -- ...should it use control codes, or hierarchical style sheets? In the end, the decree went out: Word should implement both formatting paradigms. Even though they're fundamentally incompatible... Word was in fact broken by design, from the outset — and it only got worse from there.' Can Free Software do any better, than to imitate the broken Microsoft model? Does document formatting even matter this much, versus content?"
enough said!
LyX does the handholding for you.
somehow, the major publishers have been browbeaten into believing that Word is the sine qua non of document production systems. They have warped and corrupted their production workflow into using Microsoft Word .doc files as their raw substrate, even though this is a file format ill-suited for editorial or typesetting chores. And they expect me to integrate myself into a Word-centric workflow, even though it's an inappropriate, damaging, and laborious tool for the job.
So his publisher is forcing him to use Word. I would be annoyed as well. I know at least some publishers accept PDF (and some even LaTeX). So maybe he should just choose a different publisher.
"First they came for the slanderers and i said nothing."
Yes, let's enumerate all the structural untidinesses of Word. Let's blame that application -- which held its own, against many, many competitors, not because of a megacorporation strong-arming it (remember, MS was not always a megacorp) but because it was good at doing what users wanted it to do -- for the inelegance of its data model. Let's compare it to SGML, which is so much nicer and easier and so much more elegant if you're a programmer and can appreciate that sort of elegance, and if you're not a programmer, well then for god's sake why are you touching a computer?
If you want SGML, you know where to download it.
The opinions stated herein do not necessarily represent those of anybody at all. Deal with it.
because Word is the quintessential example an app where you need a large paid development staff with varying skill sets, including many (UI design, usability, localization, QA, end user support, documentation, incorporating specialized features for customers such as law firms, integration with legacy enterprise software...) which historically have not been the strengths of FOSS.
And here's something that's often overlooked: even if FOSS could put together a team to do this (perhaps with some resources loaned by IBM or Red Hat or someone else), it's not enough to do it once. Or twice. The software has to be maintained year after year and upgraded to reflect the ever-changing requirements of businesses and consumers, and people expect professional UI design, usability, localization, QA, and doc.
Ref. Fred Brooks' article about the difference between the level of effort required to produce a "neat little tool" vs. a commercial product. Brooks came up with a factor of 9, and it wasn't just about having more folks involved... it was different kinds of folks too.
Joel Spolsky has an excellent write up on why the Office file formats suck. A must read.
http://www.joelonsoftware.com/items/2008/02/19.html
He actually worked on Excel leading to funny anecdotes like this one
http://www.joelonsoftware.com/items/2006/06/16.html
Yes, I still pine for WordPerfect 5.1, and even the early Windows versions.
Three words: Reveal, Codes, and Acerson.
With just those you could do damned near anything.
To this day, likely close to ten years since I stopped using WordPerfect, I still find myself clobbered by strange MS Word formatting edicts, with no obvious way to get rid of them.
At least with WP you could see why something was weird, and fix it.
Three Squirrels
"The last line of a right hand page should not end with a hyphen. This
has been a style rule for many years, yet it is amazing that most word
processors do not do this! I just smile when I pick up a book produced
with something like Frame and you immediately find these errors.
Needless to say, troff does this correctly, and has for 20+ years. A
friend commented to me that normal evolution would have gone Word to
Frame to troff, but instead, the computer industry has gone the other
way!"
-W. Richard Stevens, author of 7 popular technical books. [R.I.P.]
I've used Wordstar, Wordstar 2000 (or 3000?), WordPerfect, MS Word, and OpenOffice/LibreOffice writer and they all pretty much suck. Most people misuse them. They don't integrate well with other software. And they produce ugly results.
I wrote my master's thesis using FrameMaker which was quite a bit better. However, for my current document-production needs, I use LaTeX. I maintain the manuals for my company's software products and we have a great workflow for building the manuals. The same Makefile that builds the software also builds the manuals: PDF versions directly from the LaTeX and HTML versions using htlatex run on the LaTeX sources. Then a post-processor fixes things up so that our HTML documentation is linked context-sensitively from the web pages of our app, and special goodies like embedded training videos are placed in the HTML documentation at the right place.
The power and control we get from this workflow is unmatched.
That about says it. Nobody else cares. I've been using Word since it came on two 5-1/4" floppy disks and included a mouse and used every version since what? 1983 or so? (Before that I used Zardax on an Apple ][ and, of course, WordStar.)
There's not a damn thing wrong with Microsoft Word. It is quite adequate--superb, even--for 99% of the people 99% of the time. I've written several 300 page books with it, including extensive indices, sidebars, tables, graphs, and pics and it works just fine. No, you can't do EVERYTHING you might want to do with it. And you might actually have to put some time in learning how it works, but ONE thing is CERTAIN:
It's not going to go away. The chances of it going away are equivalent to the chances the United States will convert to driving on the left. Only the nerds care about the arcane details under the hood.
Nobody else gives a rip.
How about a moderation of -1 pedantic.
My number one wish for any word processor, but especially Word, is a switch that says:
I'm writing a document that will be printed out on paper with black toner.
At a minimum, I don't want e-mail addresses or URLs changed to blue, or underlined, or hyperlinked.
My number two wish is a switch that says:
Anything pasted into this document will adopt the formatting of the line into which it is being pasted.
I cannot think of a single instance, ever, when I wanted the formatting from some web page to be carried over into my document. My final wish is to find a word processor that assumes, or at least makes really easy to specify, that the Page One Header will not be used on subsequent pages. I don't recall how Word does that these days, but in LibreOffice it involves creating a style just for the first page. Assuming that you've managed to Google the specific forum post that tells you that.
Three Squirrels
Word may have flaws, like every other piece of software ever written. But it does the job. Millions of not-so-computer-savvy people are able to created good-looking documents using it.
WordPerfect relied on the embedded codes model, but they never did get it completely right. For anything non-trivial, you pretty much had to go down to the code level, hand-placing the codes to make the text render properly. Copy-and-paste across formats was often disastrous.
Word's model might be conflicted, but it works. There are very few situations where the wysiwyg editor can't get the text to look like what you want.
If I'm creating a document, I don't really care whether the encoding is HTML or RTF or docx or whatever, I just want it to look right, and Word does that.
This is not rocket science if you want Word to die write something better and cheaper the market is willing to accept over word.
I hear a lot of talk, fancy words but no hint of what would replace it or what could be done to even start to remedy the situation other than clicking your heels and wishing the evil Redmond monster go away. Talk is cheap, real monsters don't go away because you ask them nicely.
With formal printed documents becoming less popular and an increasing emphasis on on-screen presentation and collaborative editing, is a word processor still a good model to manage business information? We have far more powerful (and systematic) formatting capabilities in numerous browsers that can render HTML+CSS content.
You must be kidding. Microsoft Word has far more formatting capabilities than any HTML + CSS content I'm familiar with. Try creating text with a multi-coloured gradient fill and a drop shadow. Try representing a complex mathematical equation. Try inserting a pie chart. Try inserting a date field that updates automatically. Try rotating a block of text by an arbitrary number of degrees.
Then consider that fact that many people using word processors in business today are capable of doing all these things without knowing a single thing about coding.
Actually HTML+CSS can do all those things. Your comment about programming is weird, because presumably you would just use a WYSIWYG interface rather than writing the code by hand, the same as any modern word processor.
The real problem with HTML/CSS is that it isn't designed to format documents with precision, it's designed to describe the presentation of information. In Word when you set a font to 14pt you get a 14pt font on the screen and on your printer. In CSS setting a font to 2em or 24px results in an on-screen/paper font size that is dependent entirely on how the browser is set to render it. 2em is relative to the base font size selected by the user, 24px is relative to the DPI setting of the screen and the zoom level of the browser.
I would love it if everyone used HTML/CSS because then documents would display in my preferred way with my preferred fonts and scales, but most people just want to quickly create something that looks exactly the same on everyone's screen and on paper.
const int one = 65536; (Silvermoon, Texture.cs)
SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
Sure, very easy. Just go learn MathML, SVG, and JavaScript. Apparently your idea of the "real world" is where everyone is conversant is 4 or 5 programming languages. As opposed to what actually happens in almost every business around, where people with minimal knowledge of computers and zero knowledge of programming can produce what I described with a single, widely-known application.
The assertion that Microsoft Word should be deprecated in favour of a hodgepodge solution like yours, in the majority of situations, is laughable.
Here's an imaginary scenario: As a consultant I go into any business and say "I've got a bright idea. Let's get rid of Microsoft Word and start using HTML + CSS + MathML + XML + SVG + JavaScript + whatever WYSIWYG editors I can find for them". You know what else would be imaginary? My credibility.