OK, so I admit: I can’t get enough news about SCO. It’s like the best and worst parts of a soap opera, train wreck, and slapstick comedy all rolled up into one big, sticky ball. This week’s entry into their history of shame is a claim to own the standard Unix executable file format, which is ridiculous for more reasons than I feel like going into right now. What I took away from the whole circus, though, is that you’re playing with fire if you entrust your company or personal computing to proprietary software vendors.
I have noticed in life when you have issues that often a solution appears from the same environment at the same moment. Synchronicity challenges you to move to the next level of efficiency and quality. Problems force you to reroute and grow in new ways and directions. Once the fields have burnt the wheat may grow. Of course I would love to be able to pick my problems, hum, I mean potential solutions and have them pitched at only a slightly higher level than that of the background noise. This week I was lucky to find myself in such a mild training situation.
I’m going to make no excuses here—I was a chardonnay socialist and it’s time I came out and everyone gathered together and gave me some support. I have, from the time I was a little child been dreaming of hammers and sickles and the like, had a knee-jerk reaction to: big corporations (evil), government (evil), conservatism (evil), and stiletto heels (rank consumerist EVIL). So if you were to say “Microsoft”, I’d say “Where?
This story, Why technical writers aren’t using FOSS, appeared in on Newsforge in April, and I have to take issue with some of the assumptions.
First of all, I am technical writer, and I do use FOSS—in fact, I’m a technical writer that documents FOSS technology using FOSS tools.
I have a car, and I pay car tax that, in theory at least, pays for the roads that I drive on. I can don my driver’s gloves, expensive sun-glasses and cool-looking cap and motor anywhere on the road network in the UK—and Europe for that matter—for no extra charge, or most of it anyway. There are some toll roads where I need to pay extra. I don't have to use these as they are alternative routes, but it usually saves a large amount of time and hassle when I do.
Ryan Cartwright was quick to comment that Lenovo have since denied that any such announcement was made. Others around the blogosphere have commented that the retraction could be due to the negative response received by Lenovo when the original story broke, but honestly, I should have seen it for the fake that it was.
I'm a big believer in rights. I believe in the right to speak your mind, the right to act however you want, as long as you aren't interfering with others' rights; I even believe in more controversial rights like 'the right to die', and one of my favorites is the right to be stupid.
What do I mean by that? Well, I think that if people want to jump out of airplanes, down cliffs, or free-climb El Capitan, like Captain Kirk, they should be allowed to do that -- even though it's very clear that they may be stupid things to do that are likely to get them killed. One of the more powerful and hard to refute arguments for Digital Rights/Restrictions Management (DRM), though, is that it can be used in life-critical systems to prevent failures due to users' own modifications -- and it seems to me that this is a sticky case of balancing the right to be stupid with the right to be ignorant.
Sometimes I get the notion that everytime someone sneezes at Google, the snot shows up in 50 blogs the next day. Everyone seems to love imagining Google as the underdog in a boxing match with Microsoft, and Microsoft even seems to like playing into the role. At any rate, everyone is talking about Google's New Spreadsheet, though the reactions are somewhat mixed.
When I go to visit my mother (as I will be doing shortly) I feel like tearing my hair out. "Oh," I hear you say, "one of THOSE stories". But no, it's not. She lets me enjoy my usual sleeping habits, lets me put my shoes on the couch, and eat whatever I want. But there is one huge difference between my house and her house, and for the two weeks a year that I stay with her there is just one point of tension. I'll set the scene:
I have been doing a small amount of research on the latest Adobe/Microsoft tussle, as brought to my notice by Matt Barton’s blog entry (thanks Matt).
The first thing I found slightly frustrating was trying to obtain suitably unbiased material on the matter. The precise nature of the discussions Adobe and Microsoft had do not seem to be in the public domain anywhere, nor is the precise nature of Adobe’s gripe. The only party “in the know” to have publicised this is Microsoft, and they have obviously put such a large amount of spin on this that their ball is going around in circles. Adobe are remaining tight lipped. Therefore, while the following is based on the digging I have done, a large amount of guesswork has gone into it.
Many of the MySQL team use IBM computers by preference to do their developing on; and I know that, for some, a lot of the reason was the support for Linux.
Now Lenovo owns IBM's hardware business, but it seems they are dropping support for Linux (that's a Slashdot link, because, as always, the comments are as interesting as the story).
One of the frustrating things about standards is that so few people really follow them. Engineers, of course, like to stick to standards, and they understand the importance of explaining things in terms of standards and interfaces. “Documentation” to an engineer is descriptive—it tells you what the thing is, what standards and interfaces it conforms to, and (unfortunately), it usually relies on jargon to accomplish this. Of course, the nice thing about jargon is that it turns up pretty well on a Google search (for example, when I wanted to figure out if I was wiring my home network correctly, I got really good hits by typing: '"cat 5e" TIA 568A network "color code"'—all jargon I pulled from the diagrams that came with the tools).
“Documentation” for newbies, however is imperative—it just tells you what to do, and doesn't bother explaining. That means that instead of relying on technology standards about the thing you're actually doing, the documentation relies on platform standards. In short, it just assumes you're using Microsoft Windows, and ‘what a troublesome person you are’, if you aren't using it. Of course, we all pretend we're conforming to standards, but the truth is that the ISPs tell a few little lies (‘384kbps dn/128kbps up’—but they only have a T1 connection!), as does the manufacturer of the modem and the firewall, and me of course, who had to quietly ignore any questions about operating system in order to evade the standard ‘Oh, we don't support Linux’ response.
I have always wanted to invent a new word. Not any old word, but a word that would gets used even in the deepest, darkest corners of coffee shops in Amsterdam. Not that I would ever get to hear the word used. I don't like coffee! So let's try vistarization. The process of a sensible, definitely obvious idea degenerating into a heavy weight project that takes many extra years to complete. I have images of small spacecraft trying to divert asteroids that are going to hit the Earth.
Well, I hate to say "I told you so", but it looks like Adobe has finally revealed that its "open" standard for PDFs was, in fact, a double standard. I've been warning colleagues for years about PDFs and urging them to avoid them in favor of a more truly "open" format, but my arguments tended to fall on deaf ears. Perhaps now that Adobe has refused to allow Microsoft to incorporate "save as PDF" into its new Office suite, I'll have an easier time of it.
Over the years I’ve tried numerous distributions, and there’s been a gradual progression from what were probably the early leaders in the Linux market—RedHat for example—through to the some recent and popular examples, particularly Gentoo and Kubuntu.
The question that has been running through my head recently though is whether this is an issue of favouritism on my part, or whether it is because the distributions I use today really are comparatively better than the distributions I used 4 or 5 years ago.
Those familiar with the world of torrents may be disappointed today to hear that Pirate Bay has been raided by some 50 Swedish police. While it's certainly not unusual for torrent sites hosting links to copyrighted-data to get this treatment, I am a bit surprised that it would happen in Sweden, especially on this draconian of a scale. At any rate, though, apparently the news isn't totally bleak -- the Swedish Pirate Party is using the event to spur support for its movement to decrease the scope and reach of international copyright law.
Creative Commons is jumping on the license-rewrite bandwagon and planning to publish a draft of version 3.0 of their license modules. This has occasioned some discussion of the ways in which CC licensing can be improved (I hope to write more broadly about this later). For me, it suggested re-treading an idea that CC failed with -- the so-called "Founder's Copyright", and giving it a bit of new life via a better implementation and a little cross-pollination with free software business models. After much pounding on the mailing list, I think I've got a good idea of the shape this ought to take, and I'd like to make a condensation here of my case for "Sunset NC/ND" modules for Creative Commons.
While many people have been working on the technical challenges of providing low cost computing to emerging communities, a couple of months back I had proposed a different and related challenge to my immediate friends and free software professionals from several organizations. This challenge was not based on how to deliver ever lower cost physical computing, but rather why and how such solutions can and should be delivered through free software.
It is raining in Amsterdam and I have a nice warm feeling in my stomach from a glass of red wine. I am lucky; I am forced to contemplate the wine for the next five minutes instead of doing any real work. My Windows XP box is starting up. I have two dual boot systems at home. In the past, I stopped my house from being a GNU/Linux only shop due to Word compatibility issues, legacy games that my kids love and the Exchange server that keeps my mail whole for me at my work.
An interesting thing is about to happen to home computing—the “Desktop” that GNU/Linux never seems able to liberate from proprietary Windows may be just about to become irrelevant. Three independent, ultra-low-end computing platforms are being released—platforms that, like the first “desktop PCs” will be mostly owned by people who’ve never owned computers before. Every one of them will run GNU/Linux!