{"id":113,"date":"2008-10-24T12:24:01","date_gmt":"2008-10-24T01:24:01","guid":{"rendered":"http:\/\/scriptorum.imagicity.com\/?p=113"},"modified":"2008-10-24T12:24:01","modified_gmt":"2008-10-24T01:24:01","slug":"form-and-function","status":"publish","type":"post","link":"https:\/\/village-explainer.kabisan.com\/index.php\/2008\/10\/24\/form-and-function\/","title":{"rendered":"Form and Function"},"content":{"rendered":"

[This week’s Communications column for the Vanuatu Independent.]<\/strong><\/p>\n

[Yes, it’s a re-hash of this rant<\/a>.<\/em> ed.]<\/p>\n

As a computer geek, I\u2019m supposed to be suffused with enthusiasm and excitement over the features of the latest software. By rights, I should be the one carrying the techno-tablets down from the mountain, telling you how the latest in frobnalising ephemetry is going to change everyone\u2019s life. I\u2019m the one supposed to show you where to sign up and what to do with it once you\u2019ve got it.<\/p>\n

I have a confession to make: I hate most software.<\/p>\n

90% of software is crap. As author Theodore Sturgeon<\/a> famously said, that\u2019s because 90% of everything is crap.<\/p>\n

I save a particular loathing for word processors. For any but the simplest tasks, their interfaces are utterly ridiculous. I haven\u2019t liked a word processing interface since WordPerfect circa version 5, which ran on DOS (remember DOS?). If I had my own way, I\u2019d still be using it.<\/p>\n

<\/p>\n

Why, after over 20 years of development, do word processors suck so badly? Mostly, it\u2019s because of the WYSIWYG approach. What You See Is What You Get, besides being one of the most ghastly marketing acronyms to see the light of day in the digital era, is ultimately a lie. It was a lie back in the early 1990s when it first hit the mainstream, and it remains a lie today. The fact of the matter is that trying to do structuring, page layout and content creation at the same time is a mug\u2019s game. Even on a medium as well understood as paper, it\u2019s just too hard to control all the variables with the tools available and still have a comprehensible interface.<\/p>\n

Ask yourself, how many times have you had to reprint a report, just because you have to hit ENTER a few more times just to get a title or a table onto the right page? How many pointless hours have you spent keeping a manually generated table of contents up to date? Make a change on page 3, and now you have to re-calculate the page numbering on the entire thing.<\/p>\n

The real sin that word processors are guilty of is not that they\u2019re trying to do WYSIWYG – okay it is that they\u2019re trying to do WYSIWYG, but they way they go about it makes it even worse. Rather than insisting that the user enter data, structure it and then lay it out, they cram everything into the same step, short-circuiting each of those tasks, and in some cases rendering them next to impossible to achieve.<\/p>\n

The concept of a workflow seems to be lost on software designers.<\/p>\n

Learning how to write, then structure, then format a document (or even just doing each through its own interface) is easier to accomplish than the all-in approach we use today. For whatever reason, though, we users are deemed too dumb to create a document without knowing what it\u2019s going to look like right now, and for our sins, that\u2019s what we\u2019ve become. And so we are stuck with word processors that are terrible at structuring and page layout as well as being second-rate text authoring interfaces. They do nothing well, and many things poorly, in no small part because of the inherent complexity of trying to do three things at once.<\/p>\n

Advanced users know this already: You can apply styles to a document which, in theory at least, allow you to avoid this kind of thing. But nobody takes the time to teach you this, because, honestly, they want to create the impression that all you have to do to create a professional document is to start writing.<\/p>\n

Ask yourself: Which is more important \u2013 the words you write or the font they\u2019re in?<\/p>\n

It doesn\u2019t help that every word processor\u2019s technical implementation is poor. The Word 2003 document format is little better than a binary dump of memory at a particular moment in time. That means that even if you do apply styles and proper formatting, they\u2019re still prone to getting corrupted, or interpreted differently from one version of the software to the next.<\/p>\n

There\u2019s no changing any of this, of course. The horse is miles away, and anyway the barn burned down in the previous millennium. We\u2019ll be dealing with stupid formatting issues for years to come. We will continue to be unable to properly structure a document past about the 80th percentile, which is worse than not at all. We will continue to deal with visual formatting as our only means to infer context and structure, leaving us with very little capacity to do anything useful with the bloody things except to print them out and leave them on someone\u2019s desk.<\/p>\n

We could be doing so much more. Wouldn\u2019t it be nice to be able to take a bunch of documents gathered during the course of a piece of work and simply dump them into a database? Wouldn\u2019t it be nice if we could share the contents of a folder on the Internet in such a way that everything is automagically organised, searchable and yes, even moderately useful to others?<\/p>\n

It\u2019s possible, you know, even easy. Or it would be easy if we could just have software that didn\u2019t make it easier to ignore useful formatting tools than to use them.<\/p>\n

Doing proper formatting is not rocket science. It\u2019s a simple matter of taking a little time to set a few properties before you start writing. Once you\u2019ve got decent styles, you have them for life. From then on, if you want to use a heading, you don\u2019t have to change the font size, then bold your text, then tab it in. One little click will do all that for you.<\/p>\n

Much of the web works this way. And despite the fact that most early web authoring tools tried to turn themselves into word processors (somehow they imagined that their warts would be seen as beauty marks), the tide has since turned against them. These days, style and content are understood to be two different things.<\/p>\n

If I had my way, we\u2019d just stop using word processors at all. We\u2019d start doing everything on the web and never print again. I\u2019m more than half serious about this, actually. At least on the Web, the idea that content and presentation are separate things isn\u2019t heresy. At least on the Web, we can archive, search, contextualise, comment, plan, structure and collaborate without having to wade through steaming piles of cruft all the time.<\/p>\n

At least on the Web, we can choose which steaming piles we step into.<\/p>\n

I wish I could start recommending that people stop using Word as an authoring medium. There are far better, simpler tools for every task, and the word processor has been appropriate for exactly none of them for too long now.<\/p>\n

Sometimes you have to destroy the document in order to save it.<\/p>\n","protected":false},"excerpt":{"rendered":"

As a computer geek, I\u2019m supposed to be suffused with enthusiasm and excitement over the features of the latest software. By rights, I should be the one carrying the techno-tablets down from the mountain, telling you how the latest in frobnalising effemitry is going to change everyone\u2019s life. I\u2019m the one supposed to show you where to sign up and what to do with it once you\u2019ve got it.<\/p>\n

I have a confession to make: I hate most software.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,3,5,12],"tags":[220,227,499,559,620,655],"class_list":["post-113","post","type-post","status-publish","format-standard","hentry","category-geek","category-hard-core","category-journamalism","category-wonk","tag-form","tag-function","tag-rant","tag-software","tag-useability","tag-word-processors"],"_links":{"self":[{"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/posts\/113","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/comments?post=113"}],"version-history":[{"count":0,"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/posts\/113\/revisions"}],"wp:attachment":[{"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/media?parent=113"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/categories?post=113"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/village-explainer.kabisan.com\/index.php\/wp-json\/wp\/v2\/tags?post=113"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}