Glyn Moody's blog

Photosynth is one of the most exciting programs I've seen in a long time. It takes a group of photos, typically of a single geographical location, but possibly taken at different times by different people, analyses them for similarities, and then stitches then together into a smooth-flowing, pseudo-3D panorama. It's really great. Just two problems. One: it won't run on GNU/Linux; and two: it's from Microsoft, and so is unlikely ever to do so.

My question is this: Why didn't the free software community come up with Photosynth first?

As a computer journalist for the last 25 years, I've received a lot of review copies of software. As something of an obsessive magpie, I've tended to keep most of it, “for reference”. Until yesterday, that is, when I finally threw out all those copies of OS/2, Lotus SmartSuite, and my entire collection of Microsoft software. This included Windows NT 3.5, Windows 2000, Microsoft Office and many, many more. What's makes this little spring-cleaning exercise particularly apt as well as cathartic is that all of us - and not just me - may finally be witnessing the end of the Windows era.

A new global standard for the enforcement of intellectual monopolies is currently being discussed by representatives of the United States, the European Commission, Japan, Switzerland, Canada, Australia, Korea, Mexico and New Zealand. This new agreement is so important that it must be drawn up in secret, safe from the prying eyes of little people like you and me. Thanks, however, to the indispensable Wikileaks, a discussion paper outlining some of its possible proposals has surfaced, and from this it is clear that it represents a serious threat to online liberty in general, and to the practice of free software in particular.

The announcement by the GNOME Foundation that it is appointing Stormy Peters as its Executive Director confirms a suspicion that I've harboured for a while: that we are witnessing the evolution of major open source projects into new kinds of players in the computing world, ones that require full-time staff not just to run them, but also to articulate what exactly they are trying to do *beyond* the code.

Three things are striking about the recent launch of Firefox 3. First, the unanimity about the quality of the code: practically everyone thinks it's better in practically every respect. Secondly, the way in which the mainstream media covered its launch: it was treated as a normal, important tech story – gone are the days of supercilious anecdotes about those wacky, sandal-wearing free software anoraks. And finally – and perhaps most importantly - the scale and intensity of participation by the millions of people who have downloaded the software in the last week.

But the question has to be: what now? How can we harness that amazing spirit, to make the Firefox Effect permanent, not just a media event that comes around once every few years?

As you may have noticed, Firefox 3 is released today. Excited by this prospect, the first thing I did when I got up was to rush to my computer to download it (yes, pathetic, I know). And what do I find?

Like many Linux Journal readers, I have been upgrading my Gibbons to Herons recently. And like many readers, I imagine, I have been finding a few little challenges along the way. That was no surprise, since it's pretty much par for the course when carrying out a major upgrade. But something else did surprise me, although in retrospect I see that it shouldn't have.

Most of the time, Microsoft's public declarations are pretty easy to parse. A bit of pre-announcement here, a touch of FUD there, with the odd dollop of feel-good waffle thrown in for good measure. Occasionally, though, it produces what can only be called a googly – not to be confused with a Google – with announcements like this one about adding support for ODF in Microsoft Office:

Captain Charles Boycott was an unfortunate chap. Not only was he the object of prolonged social ostracism, but his name has passed into history as both a noun and a verb describing that action. At the moment, the idea is much on people's minds because of suggestions that the Beijing Olympic games should be boycotted, but here I want to discuss something quite different: whether the open source community should be boycotting Microsoft, and if that is even possible.

There are many ways of peering into the future. This page lists 163 of them, including cephalonomancy (divination by boiling an ass head), coscinomancy, (divination using a sieve and a pair of shears), ololygmancy (fortune-telling by the howling of dogs) and tiromancy (divination using cheese). Me, I prefer to stick with the tried-and-trusted method of reading between the lines of Microsoft press releases.

I have been covering Microsoft for over 25 years - I've even written a few books about Windows. During that time, I've developed a certain respect for a company that just doesn't give up, and whose ability to spin surpasses even that of politicians. To be sure, Microsoft has crossed the line several times, but it has always worked within the system, however much it has attempted to use it for its own ends. No more: in the course of trying to force OOXML through the ISO fast-track process, it has finally gone further and attacked the system itself; in the process it has destroyed the credibility of the ISO, with serious knock-on consequences for the whole concept of open standards.

Almost exactly one year ago, I made the following suggestion in the wake of Dell's long-awaited decision to offer ready-configured GNU/Linux systems alongside the usual panoply of Windows systems:

we must vote with our wallets. Assuming the Dell GNU/Linux systems are not hopelessly flawed in some way, we must all try to buy as many of them as we can (within reason, of course).

What follows is a short report on my own experiences of putting my money where my mouth is.

News that Microsoft is to be hit with yet another fine from the European Union has naturally attracted plenty of attention, but it has also raised the old questions of whether such interventions by governments are justified or even do any good.

Yesterday, Microsoft announced DreamSpark – an ironic name, since it actually lays bare Microsoft's worst nightmare: that more and more of tomorrow's programmers are growing up using free software for their studies, which means that as they move out into the world, there will be less and less demand for Microsoft's tools, and even fewer programs written for its platforms.

There's no doubt that 2008 will go down in history as the end of the first Microsoft era. This year, Bill Gates will finally hang up his Microsoft mouse and leave the company he cofounded over 30 years ago. Most people know that he's going off to spend the very large sums of money he has acquired from those Microsoft years, most of which has been used to set up the Bill & Melinda Gates Foundation with $37.6 billion in assets. But what will that really mean for free software?

It's not every day that the entire technical press goes bonkers over news in the open source world, but that's what happened last week, when Sun announced that it was buying MySQL. Doubtless, the pleasant roundness of the sum involved - $1 billion – helped, as did the fact that most of that was cash. But leaving aside the sense of satisfaction that events in the free software world should be suddenly thrust centre-stage, Sun's move does raise a larger question about the fate of all open source start-ups.

Defending Openness

September 21st, 2007 by Glyn Moody

Things have been going pretty well for open source and open standards recently. First, there was the implosion of the SCO case, in the wake of which even SCO accepts that it may not be around much longer. Then we had the rejection of Microsoft's request for a fast-track approval of its OOXML rival to ODF. Finally, the European Court of First Instance has refused Microsoft's request for an annulment of the terms imposed by the European Commission. All are notable victories that many regarded as unlikely a few years ago. But elsewhere, other open movements are still in the early stages of the struggle against forces pushing closed, proprietary standards.

The Joy of OOXML

August 30th, 2007 by Glyn Moody

For most of us, file formats are right up there with printer drivers in terms of fun. Certainly, they're important, but not something you'd look to for excitement. And yet that is precisely what the battle between the OpenDocument Format and Microsoft's OOXML is providing. And I'm not just talking about the dry, intellectual excitement derived from comparing well-formed XML tags: this is a no holds barred, down-and-dirty mano a mano fight over the soul of document standards.

No one would have believed me if I had said five years ago that Microsoft would have a page on its Web site called “Open Source at Microsoft

Most people in the free software world know two things about Apache. The first is that its name derives from the fact that it was “a patchy server

Syndicate content

Featured Videos

The X Window System is a magnificent platform for many uses, but using it to run an application over a slow network is nearly impossible. This is an introduction to NX, a technology that makes remote applications fly even over commodity internet.

Linux Journal Gadget Guy, Shawn Powers, reviews the Flip Video Ultra, a small portable video camera, and shows us how easy it is to edit the video with Kino.

Thanks to our sponsor: Silicon Mechanics

From the Magazine

September 2008, #173

Feeling a bit like a Thermian? Never give up, never surrender! Someday, you could go from underdog to top dog. Just take a look at a few of the underdogs we highlight in this issue: Mutt, djbdns, Nginix, Gentoo, Xara and the program voted mostly likely to fail just a few years back—Firefox. If Firefox not radical enough for you, check out Chef Marcel's column for some more alternatives. Having trouble mapping your program data to your relational database? If so, Rueven Lerner shows you some tricks in his At The Forge column.

Need to run GUI applications on your server in the next state? In his Paranoid Penguin column, Mick Bauer shows you how to do it securely. Kyle Rankin keeps hacking and slashing and shows you a few split screen secrets you may not be familiar with. Finally, we all know what happens next February, but only Doc knows what happens afterward.

Read this issue