Skip to content

Caliban – Opinion and Righteous Anger

Ian, Sarah, Eloïse and Lucas kick against the pricks.

Archive

Category: Technology

Back when Tim Berners-Lee invented the World Wide Web, it all seemed so simple. Gopher, a means of sequentially browsing through hierarchically structured, text-based information, would be replaced by a technology that offered random access to information, information that need no longer be purely textual in nature, but which could include images and sound. And so it came to pass that hypertext, as we know it today, was born, along with its transfer protocol.

That was then, but this is now.

I’m glad I learned to write HTML in those early days. It was so simple: learn a few tags, mark up the structure of your document, indicating the headings, the subheadings, the paragraphs, the words requiring emphasis, the program code and the already formatted sections of the document, and then this great piece of software called a browser would render your document accordingly. The results even looked good.

There weren’t too many tags to learn. With nothing more than a basic HTML tutorial, one could be marking up one’s CV or writing an article within the hour. Within a few days, one had pretty much gained familiarity with the entire scope of HTML as it then existed. Marking up a document was conceptually confined to indicating the inherent structure of the document. Rendering was the job of the browser, perhaps under influence of the reader, who was free to express his preference for certain colours and fonts. There were few means for the document’s author to influence the rendering of his document, because that had nothing to do with the content. Even the <FONT> tag hadn’t been invented yet, and would cause a great amount of controversy when it was. Back then, people argued about the usage of <STRONG> vs. <B> and <EM> vs. <I>, the former content-based and therefore approved by the hypertext moralists, the latter presentational and therefore a threat to the logical purity of the Web.

If I were starting out authoring documents for the Web today, it would be an entirely different experience. On today’s Web, document authors — even the term itself seems quaint now — are as much, if not more, concerned with the presentation of their document as its content. In fact, one could even argue that the presentation has, to a large extent, become the content.

This is due in no small part to the mass commercialisation of the Web. You have to remember that, in the first years of the Web, commercial entities were unwelcome. People didn’t want big business polluting the Web. There was no Amazon, no eBay and no Google. AOL was still a separate, proprietary network, the term social networking hadn’t yet been coined and it was still hard to search for information. The Web then was still a niche product, offering little of interest, except to computer geeks and academics. Mathematicians and computer programmers are a lot less concerned with house style and brand recognition than multinational conglomerates, and the presentational technology of the Web reflected that.

These days, however, we have technologies like CSS and JavaScript to contend with. The View Source menu option of the browser used to yield insight into the structure of a document, providing hints on how to mark up one’s own. These days, it merely provides keyhole entrance to the haystack, in which to begin one’s search for a particular needle. Today’s documents have a <HEAD> section as large as the <BODY>, and frequently include multiple stylesheets and JavaScript libraries, used to stylise the presentation and effect dynamic, event-driven updates to the page. Attempting to localise the snippet of code or the particular style responsible for a certain effect can take minutes or even hours, rather than seconds. Styles are object-oriented and therefore frequently layered on top of one another, making it sometimes hard to unravel which particular combination of properties is responsible for a given rendering.

Most of the time, I manage to remain blissfully ignorant of the complicated nature of modern Web authoring. I use comprehensive blogging software and a mark-up plug-in to make the experience of writing prose on a computer as close as possible to that of using an electric typewriter. I’m more concerned with getting words onto the page than I am with serving you distracting animation or polyphonic sound while you read. Sorry. Not that these things can’t enhance your reading experience; just that I’m not as concerned with them.

The recent move of this blog from Movable Type to WordPress brought me into close contact with the inner ugliness of the modern Web. Before I knew it, I was wrestling with page layout and legibility issues, when all I wanted to do was write. Visual themes take away a lot of the headaches, but they also add a few of their own. No theme suits me without some modification, but before one can set to work on this, one must learn the structure of the theme, the styles it uses and how it relies on JavaScript. That can be quite an investment of time and energy. Small modifications often don’t have the intended effect and it can take multiple attempts and a lot of hair-wrenching to get things working exactly as you want them. Before you know it, you’ve got a dozen browser tabs open at various works of reference on CSS and JavaScript.

A good case in point is the automatically expanding box in which this paragraph is written.
 
You have no idea how long it took me to get this to work the way I wanted. I needed it for the in-line
examples of code that I sometimes post, which wouldn't otherwise have fit. Even the current
behaviour is a compromise, because I couldn't get it to do exactly what I wanted.

If you’ve got a slower computer or you ever browse the Web on a phone, you will have felt the proliferation of Flash around the Web. Huge applets that add little or nothing of value, often just mundane advertising, seem to crop up on the pages of just about every large site these days. I block these with a browser plug-in, but in the worst cases, the site is inoperable without them. All too often, the entire page consists of a single interactive piece of Flash. If one has a broadband Internet connection and a powerful computer, the effect can be impressive, but this should never come at the expense of accessibility. Flash, and other such fluff, is a nice way to enhance a page, but a site should never be reliant upon it. All too often, Web authors rely on it for core functionality.

Such authors are missing the point of the World Wide Web. They, along with those who advise us that their site is “best viewed with version Y of browser X” are, perhaps unwittingly, actively undermining the pioneering work of those whose designs, based on open standards, make the Web even possible in the first place.

So, we’re seeing a shrinkage in the universal accessibility of the Web. The Web may be world-wide in scope, but its usability is no longer global. We’ve strayed a long way from the ideal.

And yet, there’s a trend far more disturbing than the one towards form over content, packaging over product. It’s bad enough that presentation has, to a large degree, subjugated content, but much more worse is the voluntary surrender of publishing liberty.

The Web was conceived as a universally accessible network of documents. Content was unencumbered, freely available to all. The blogging revolution seized upon this principle and a new paradigm of amateur journalism and publishing was born, in much the same way that desktop-publishing had caused a minor revolution in the off-line publishing world fifteen years earlier.

In recent years, however, we’ve seen a disturbing trend towards authors willingly choosing to publish their work in a limited access forum. Take, for example, those authors who write exclusively on Facebook or one of the other so-called social networking sites.

Ten years ago, the Web was home to millions of highly individualistic home pages, the unique calling card of each individual author. All were created from scratch, so no two looked exactly the same.

Later came the blogs and, whilst the advent of easy to use blogging software and blog hosting sites was deleterious to the unique appearance of the personal home page, that appearance could still be modified at the will of the user and, much more importantly, access to the content was still universal.

Compare that with today’s voluntary retreat into the proprietary territory of services like Facebook. Users post not only instantly disposable one-line status updates, but also extended articles, photos and other content. Prior to the rise of social networking sites, such content would have been posted in a publicly accessible domain, but is now consigned to the proprietorship of a corporate entity, where it remains inaccessible to non-members. Not only that, it is also forced into the creative corset of the Facebook house style. The negative impact is both to the author, in the form of creative restriction, and to the reader, in the form of drastically reduced accessibility.

This voluntary surrender of free and uninhibited access on a massive scale is truly a lamentable development in the evolution of the Web and hearkens back to the bad old days before the mass adoption of the Internet, when companies like Compuserve, AOL and Microsoft tried to lure users away from the Internet with the promise of a superior, parallel network infrastructure containing higher quality content produced by experts.

Similarly, Facebook is in the business of appropriating authors and their content on a massive scale, because the more people there are on Facebook, the more reason there is for those not on Facebook to get on Facebook. It’s a subtle form of coercion, with the users themselves as the catalyst. It’s harder to blame the company than it is the dimwits who have made it what it is today.

The poor bargain that is being made by users who surrender their freedom to the likes of Facebook is one of which most of them actually remain unaware. Those who consider the matter at all doubtless feel that the trade-off is a worthwhile one, and that the service has reached such critical mass that it can scarcely even be considered proprietary any more. After all, anyone is free to open an account and partake of the content. Whilst it’s true that anyone can become a member, most of the content will continue to remain invisible to me until its author acknowledges me as a friend. Besides the accessibility issues, there are many other reasons to resist the Facebook hegemony, which I won’t go into here.

In removing from the public eye content that would otherwise have been readily digestible by anyone anywhere in the world, Facebook is building a compelling case for non-members to join. After all, how can we afford not to, when all of our friends, family members and colleagues have apparently already done so? If you can’t beat them, should you not join them?

I believe the only possible answer is a resounding No!

The Internet is the single most important invention in our lifetime. Its omnipotence flows directly from the universal nature of its content, content that is served up using technology based on open standards. Users who willingly donate their creative work to the exclusive pool that companies like Facebook use to justify their valuation as access providers of that content undermine a truly world-wide Web. That creative work is subsumed and becomes a fractional enlargement of the body of proprietary content that Facebook uses as a compelling argument for the rest of us to join.

You don’t need Facebook to stay in touch with your friends and you certainly don’t need it to enable you to reach people with the written word.

Make no mistake: Facebook is not free. There is a very real price that all of us pay if you use it.

As the man once said, freedom’s wasted on the free.

It’s been a while since a new version of Ruby/AWS was released. In fact, it’s been more than eight months since version 0.7.0 first saw the light of day. I often don’t even mention new releases here, because they’re of such limited interest.

To prove there’s still life in this old coder’s brain, however, I’ve been working on version 0.8.0 for the better part of the last week.

That work has involved my least favourite type of coding: rewriting from scratch. Specifically, the implementation of batched requests and multiple operations had become unmaintainable. I could no longer read my own code, even with plenty of comments. Worse, there were bugs that needed fixing and it was impossible to set to work for fear of introducing new gremlins.

So, there was really no way around it. I kicked a new approach around in the back of my head for a couple of days and, when I was ready to commit some time to coding, sat down at the computer, deleted the methods related to the old implementation (to prevent them from negatively influencing me) and set about reimplementing the features from scratch.

The work was quite painful, but I’d expected that, which is why the rewrite had been postponed for as long as it had. In the course of writing the new implementation and producing unit tests for it, bugs came to light that had gone undetected in the old implementation. These have now been dutifully squashed.

If you need programmatic access to Amazon’s catalogue and shopping cart facility, I urge you to look at Ruby/AWS. It’s almost two years old, maturing well and takes a lot of the headaches out of querying for Amazon’s products.

The full list of changes in 0.8.0 can be found on RAA.

It turns out that my first dedicated network drive, a LaCie Big Ethernet Disk, wasn’t dead as I suspected after all, merely in a state of suspended animation for the last eighteen months.

I’ve regularly returned to this LaCie drive over the last year and a half, because it housed some unessential data for which I had no back-up of. I’ve always hoped I could one day find a way to get at it again.

So, I returned to the unit again a few days ago, expecting another bout of brief head-scratching, followed by consignment of the device to the cupboard until the next time my curiosity auto-piqued.

This time, I decided to completely dismantled the thing. Why worry about rendering void an expired guarantee?

I thought I’d been hearing the drives spin up during my irregular tests over the last eighteen months, but what I’d actually been hearing turns out to have been the sizzling of the power adapter block. Seriously, up close, it sounded like bacon being fried, but from a distance, the sound was inseparable from that of spinning drives. Anyway, the drives themselves, as it turned out, were silent when I put my ear next to them. A good sign, to be sure.

I hadn’t previously suspected the power supply, because the blue light on the front of the drive housing was illuminated, as were the LAN lights at the back. This obviously meant that the drive was receiving electricity, at which point I ruled out the power supply as the possible cause of the problem. That left only the hard drives themselves and if those were buggered, well, game over, right?

A quick Google search now revealed many more similarly broken drive units than when I had first looked for others afflicted with this ailment back in June of 2008. Lo and behold, many people reported the same sizzling power supply problem, and the fact that the unit hadn’t completely shuffled off its mortal coil, but merely declined to the point that it could now power only the lights on the casing, not spin up the discs inside. Another very good sign!

I wish I had realised earlier that it was only the power supply at fault. I hadn’t even contacted LaCie at the time, believing the unit to be no longer under guarantee, its being just over a year in my possession. I also didn’t realise that a power supply unit could partially die and then stabilise at some drastically suboptimal level, the way many LaCie units apparently have.

It turns out that LaCie actually offered a two year guarantee on units back then (in Europe, at least), so I should have contacted them. If nothing else, they would have replaced the drive.

More likely, they would have known what was wrong and just supplied me with a new power supply free of charge. More fool me for not looking into it.

Incidentally, in case you run into a similar problem, you should be aware that LaCie currently offers a three year guarantee on new drive units.

I opened a ticket with LaCie, but they were adamant that they wouldn’t help me, because the drive is all of 2½ years old now. My retort that it had died when it was only one year old cut no ice with them.

I would have liked them to demonstrate a little more understanding, particularly in view of the fact that so many other users’ drives have had exactly the same problem, but they’re obviously not that kind of company. Some manufacturers will bend over backwards to help any customer with a problem, whether the unit is still under guarantee or not — just in the name of good customer service — but that’s only some companies; not LaCie.

Now almost certain that only a faulty power supply was standing between me and my old data, I bit the bullet and ordered a replacement from the LaCie Web site. At least they actually sell the accessory on-line. I had half expected it to not even be separately available, which would have been a problem, because it has a strange, proprietary four pin connector that meant no-one else’s adapter could be substituted in its place. Why do companies do this? I’m unpleasantly reminded of the 1001 different charger connectors that Nokia mobile phones have sported over the last fifteen years.

Anyway, for around €40 plus postage, I ordered a new 57W adapter. To LaCie’s credit, they did at least send it promptly.

Once it arrived, I plugged in the unit and, sure enough, the drives span up again.

A switch port mirroring and tcpdump session was required to figure out which IP address the thing was attempting to latch onto, and then I was able to log in and configure the drive again.

With that done, I took it down to the equipment cupboard and connected it to the UPS and core switch.

The next twelve hours saw the ReadyNAS pulling 56 Gb of data off the LaCie, where it’s now better protected against the vagaries of cheap consumer electrical goods.

I feel pretty daft for having remained in the dark for so long about such a trivial problem and its equally trivial fix, particularly as it ended up costing me not only time without my data, but also money for a new power supply.

I was even wrong about this being a single drive unit. Opening it up revealed two 320 Gb drives, not the single 640 Gb drive I was expecting to find.

The irony is that I currently actually need a USB drive for the purpose of back-up, but this one can only be connected over Ethernet. I wouldn’t really mind, but I have to mount this drive over CIFS, which is less than ideal on an almost exclusively UNIX-like network (and especially when you consider that the LaCie unit actually uses XFS internally). The drive has a USB port, but annoyingly, it can function only as a USB host, which means that you can connect other devices and have the LaCie present them for use, but you can’t make the LaCie subordinate to another device that is serving as a USB host.

Since I’ve already got two ReadyNAS units in the house, one of which has an external Seagate drive connected over USB, I’d like to connect the LaCie to the other one. If both devices can only host other USB devices, however, doing so isn’t going to get me anywhere.

Eye Candy

Feb 7 2010

I mentioned in a recent posting that I’ve worked my way through quite a lot of window managers in my time, and that the dull but functional Metacity has been my steady friend for seven or eight years now.

The recent acquisition of powerful new hardware inspired me to read up on what modern desktops can now do, given a fast GPU and lots of video RAM. It didn’t take long before I was reading about Compiz.

Actually, I’d heard of Compiz a few years ago, but knew no more about it than that it was a compositing window manager. And that’s all I needed to know at the time, because my video hardware from 2003 would have been instantly brought to its knees by Compiz.

Now, however, I have a machine that is more than a match for what Compiz can throw at it. Inspired by what I’d read and the accompanying screenshots, I installed the necessary packages and fired it up.

At first sight, not much had changed. Everything looked the same, from the title bars of the windows down to the look of the context menu that appeared when I right-clicked on those bars. That’s because my existing GNOME theme was still being applied. Compiz really does just manage the behaviour of the desktop and its windows. Window styling is handled by a window decorator, of which there are a few. I’ll get back to this later.

There’s a lot to configure with Compiz. Be prepared to lose several hours in your first session with it. The way it looks and behaves can be radically altered, so that no two systems running a Compiz desktop need look anything like one another.

Compiz on its own doesn’t do very much. It relies on an architecture of plug-ins to achieve its multitude of effects. One very common such plug-in is that of the Desktop Cube.

Linux users will typically configure their desktop to comprise a number of virtual desktops. The physical monitor can be thought of in this context as a sliding window, displaying only one of those virtual desktops at any one time. My physical desktop, for example, measures 3940×1200, but I have four virtual desktops configured in a single row, which gives me a virtual desktop size of 15760×1200. I could have configured those four desktops to be a 2×2 grid, which would have given me a 7880×2400 desktop. You switch from one virtual desktop to another with a key or mouse combination, which makes it convenient to use each desktop for a different kind of application. You might use one desktop for general work, for example, another for graphics work, another for programming and yet another for music.

That’s how things have been in the UNIX world for a long time. It’s crippling to have to use a computer with no virtual desktop configured. Everything feels impossibly cramped, as if you’ve suddenly had to move all of your belongings into a single room in your house.

Compiz’s Desktop Cube plug-in adds to this facility the notion of a third dimension. Now, I can turn my row of four virtual desktops into the side faces of a cube, adding a photo of my children on the top and bottom faces, for aesthetic purposes. I can still navigate to any particular desktop with the same key combination as before, but now I can also zoom out and get an overview of the whole cube from somewhere in the desktop cosmos with updates to each face in real time. Adding the Rotate plug-in, I can rotate the cube in any direction to view it from any angle. I know it sounds bizarre, but in this way, you can angle the cube such that you can easily see the progress of applications on two different desktops.

If you configure your cube with some degree of transparency, you can even peer through the foreground faces to see what’s happening on the opposing faces, albeit the mirror image of them (because you’re viewing them from behind, as it were), but that’s stretching practicality. It’s better to just rotate the cube 180°.

The fun doesn’t end there, of course. You can configure the Cube Reflection and Deformation plug-in. The reflection part make it appear as if your cube is hovering above shiny glass, whilst the deformation part allows you to turn your cube into a sphere, a cylinder or an oval. I prefer the delineated regularity of a cube, however, as it makes it obvious which desktop each application is on. Conceptually, I find it difficult to think of my configuration of virtual desktops as anything other than a grid of flat surfaces.

Anyway, a picture’s worth a thousand words, so here’s a shot of my cube. You’ll notice there are actually two cubes, one for each of my monitors. Although my monitors are configured to each show half of the physical desktop, I opt for multiple desktop cubes here, because the alternative is a ten-sided cube instead of six, on account of the extra four side faces that have to be squeezed onto a single cube. It’s more logical to me, when zoomed out, to be looking at one cube per monitor, each of which displays the desktops available on that side of the monitor. Clearly, the concept of a cube needs to be taken figuratively when configuring Desktop Cube.

Compiz Cube.

Compiz Cube in action on a dual-headed desktop.

Hopefully, that makes things a little clearer. Here, you can see my general work area, including mutt mail client, on the left-most face of the first cube. On the second face, you can see the Sonos Desktop Controller, running under WINE.

On the second cube, the first face has MythTV is playing the local news on AT5, whilst the second has the latest build of Chromium open at Google Reader.

I want to demonstrate one more plug-in, called Expo. Expo allows you to zoom out on an unfurled representation of your cube. You can unfold your cube using just the Desktop Cube plug-in, too, but you’ll see only as many faces as fit on your display. With Expo, all of your desktops are displayed in a scaled fashion and updated in real time. You can then double-click one to go to whichever desktop you want. Where Expo’s unfurled cube really beats the standard unfolded Desktop Cube, however, is that you can even drag windows from one virtual desktop to the other.

Again, it’s easier to show you a pciture of Expo in action:

Compiz Expo Plug-in

Compiz Expo plug-in in action.

Desktop Cube and Expo are just two of the dozens of plug-ins available to Compiz. Others include Animations, which will allow you, amongst other things, to see your windows disappear in a blaze of flames when you close them. Wobbly Windows will give you windows that do just that: wobble and stretch when you drag them.

What Compiz is to desktop and window behaviour, Emerald is to styling your windows. Using Emerald, you can make your title bars, borders and buttons look any way you want. I won’t go into the details here, because it’s much more rewarding to just try it out, but my window title bars now have six buttons, including buttons for rolling up the window like a blind, making the window stay on top of others and making the window visible across all virtual desktops. The widgets even pulsate when the mouse cursor is held over them.

It’s a common misconception that, if one likes what the Americans call eye-candy, superfluous fluff that eats RAM and CPU time, but is nevertheless visually appealing, one has to run MacOS X or even Windows 7. What’s possible on those operating systems pales, however, in comparison with Compiz. If you pair Compiz with Emerald, you have a degree of configuration at your fingertips that can render your computer unusable by anyone else but you (or even including you, if you’re not a little cautious).

That’s actually no coincidence and therein lies a key reason why free desktops triumph over closed desktops. At the end of the day, Apple and Microsoft want a computer running their desktop to be instantly recognisable, no matter how it has been configured. That’s why they don’t allow you to stray too far from the default, even if you change everything that they allow you to.

Using a free desktop, on the other hand, the world is your oyster. You can choose any desktop environment, such as KDE or GNOME. You can then apply any window manager you want, of which there are dozens. Add a window decorator to the mix, with more themes than you can shake a stick at, and you have the ability to make your desktop look unlike any other.

The major downside of this flexibility is that other people’s computers become very awkward to use, to the point of feeling utterly impractical, because their behaviour is so far removed from what I’m used to. Just having to click on a window to raise it above others is an unacceptable inconvenience when you haven’t had to do so for fifteen years. Similarly, why do I have to hit Ctrl-C in Windows to copy data to the clipboard? I’ve already highlighted what I want to copy, so why doesn’t just the act of highlighting it make the system copy the data in question to the clipboard for me? After so many years of wondering that, the question is almost rhetorical at this point.

Another downside is that the lack of brand recognition that this degree of configuration flexibility provides is part of the reason that domination of the desktop by Linux hasn’t happened as some people expected it to. The Linux desktop has no ubiquitously recognisable face, nor can it be assumed that any two Linux desktops can even be operated by applying the same assumptions regarding keyboard and mouse behaviour.

These downsides are mere annoyances, however, compared to the alternative of surrendering the power to mould your desktop to your needs.

Once upon a time, as an avid computer user and someone who even made his living in the field of IT, I used to regularly revisit my working habits and make incremental refinements to my methods and the set of tools I used on a daily basis. Over the years, this led to more efficient work practice and a better understanding of how the tools in particular and the system in general functioned.

In recent years, though, I suppose I’ve become set in my ways. I don’t evaluate new software nearly as often as I used to, and tools that I’m comfortable with and have used for years are rarely, if ever, reassessed to determine whether they’re still the best ones for the job.

Hardware isn’t immune from the phenomenon, either. Take the TrackPoint (nipple-like pointing device) on IBM/Lenovo Thinkpad laptops, for example. While most of the mobile computing world has since moved to a touchpad, I still hate the bloody things, because it’s impossible to avoid touching them by accident and they require one to take one’s fingers off the keyboard.

I’ve tried time and time again to adjust to a touchpad, because fewer and fewer laptops are still manufactured with a TrackPoint, but I can ultimately reach no other conclusion every time than that it really is an awful invention.

This choice (which is no choice at all) means that range of laptops available to me is now pretty much restricted to Thinkpads. At least they’re excellent computers, or I’d be left with nothing.

Similarly, even if I didn’t have ideological objections to Apple as a company, which, by themselves, are reason enough to boycott the company, there are the numerous usability issues with both their software and hardware, not least amongst which is their wretchedly handicapped single-button mouse, surely the stillborn child of the input device world. What’s next? A keyboard with a single key? Ovine Apple fans would still lap it up, I suppose, as long as it was shiny and white.

That’s fodder for another posting, however. This one is, as stated at the beginning, about software and working practices.

I once programmed and wrote e-mail in Emacs. After a few years, I moved to Vim, which I’ve been using ever since.

Similarly, I once read news (in the Usenet sense) with TIN, but then moved to slrn, where I still am (although I hardly read news any more).

What about shells? A little know fact is that I was briefly a tcsh user before moving to bash, where I was happy for years until I discovered that almost everything I liked about bash had been implemented in a turbo-charged fashion in zsh. I’ve never looked back.

Window managers have seen more varied use. I started off with fvwm2, but that was too awkward, so I moved to NeXTSteP clone, AfterStep. Then came a brief flirtation with Enlightenment, which was too unstable and unwieldy at the time to truly consider adopting, so I instead moved to WindowMaker, which was basically a slicker AfterStep with easier configuration. I eventually abandoned the concept of the highly configurable window manager and switched, almost incidentally, to the de facto GNOME standard of Metacity. I tried many more along the way, of course, but only the above were used for any great length of time.

By that point, much of the functionality commonly associated with the window manager had been extracted to the wider desktop environment, most commonly GNOME and KDE, leaving Metacity with little more to do than decorate and manage windows. One of the great things about WindowMaker, for example, was its dock. Metacity had no such feature, but GNOME offered a similar feature called the panel. At that point, window managers had all but ceased to be an interesting category of software. I had gone through a series of them, each more heavily-laden with features than the last, to ultimately adopt one that was very lightweight.

Programming languages have undergone similar scrutiny in the course of my computing life. Ten years ago, most of the programming I did as a system administrator was in Perl. Be it number-crunching, analysing log files, parsing text or writing an interface through which two pieces of software could talk to each other, Perl was the tool I reached for.

The nature of the job of a system administrator hasn’t changed much since then, but since 2002, I have been using Ruby almost everywhere that I would previously have used Perl; the sole exception being throwaway one-liners, such as quick text substitution. It’s still hard to beat Perl for that.

Since I stopped working as a system administrator, I’ve had only my own (home and remote) systems and network to manage. I suppose I must have overdosed on technology at some point, because I haven’t felt the need to keep up on new developments over the last four years. Part of that is because of the illusion of free time that retirement has created. I no longer feel cornered into the evenings and weekends by my work schedule, so in theory, each and every day can be turned into anything I want it to be, including a productive day of learning, honing one’s skills.

It doesn’t work out like that, however. Without the constrictions of a work schedule to underscore the precious nature of free time, I find myself putting off until never that which I could do today. I can shove some of the blame onto my children, too, of course, who are a big drain on my time and energy, but it’s a bit disingenuous. My own lack of self-discipline is the real problem here.

There was once a time that I read the Linux Weekly News every week. If I was going on holiday, I’d print it out and take it with me. The rain forests suffered, but my knowledge increased over time.

I used to read the kernel developers’ mailing list, not because I was one of their kith, but to keep up on the direction in which Linux was travelling and to find out what new features were being developed.

When a new release of Red Hat Linux would come out, I would check to see which new packages had been added since the last release and then research each of them to see if any useful new tools had been added. This was guaranteed to expose me to new tools, which often revealed new approaches to old problems, as well as areas of technology about which I was basically ignorant.

Perhaps the most amazing to me now is that I would, on a more or less annual basis, read all of the man pages on the system, to see which familiar commands had acquired new features and options that I could put to good use in my work. It was also a good way of reminding myself of the existence of the more obscure tools available in the UNIX world. You’d be surprised how many talented, senior admins I’ve met who have never heard of tac and rev, for example (which aren’t even that obscure).

The time has come to mend the error of my ways and rediscover some of those good practices.

That’s partially what the migration of the blog from Movable Type to WordPress was about, as was my attempt to teach this old dog new browser tricks with Chromium. Yes, they’re not a branch of rocket science, but that’s not the point, either. The point is to find inspiration again. To make fire, you first need a spark, and I chose browsing and blogging software to be my first pieces of flint. Once that fire is lit and the snowball starts to roll, I won’t just have poorly mixed metaphors, I’ll have momentum, too.

There’s nothing wrong with old technology and working practices. Not all change is progress. On the other hand, it’s important to move with the times and not just cling to the old out of ignorance.