LWN.net Logo

The Grumpy Editor's 2008 retrospective

By Jonathan Corbet
December 24, 2008
Holidays are an exercise in tradition. One of the more charming holiday traditions around LWN is to look at the predictions made at the beginning of the year and measure them against reality. There is, after all, great value in things which make us laugh. This year's predictions were featured in the January 3, 2008 edition. As might be expected, some of them were better than others.

What was predicted

Your editor's first prediction was that support for Flash playback would mature in 2008. In some sense, that may be true. Your editor's desktop system, running the Rawhide build of Gnash, can now faithfully display a wide variety of Flash ads, web site "intros," and various other thoroughly useless bits of media. A Flash-based "interactive tour" offered by LWN's bank worked nicely. But support for many other Flash features, including audio and simple playback from online sites, still is not especially solid, and other interactive Flash applications do not work at all. This problem, it seems, is still not solved.

The prediction of the KDE 4.0 release required little in the way of foresight, as did the prediction that users would be unhappy. That stage was well set before the beginning of the year. A continued focus on power management was also an easy thing to foresee; there will be great value in making our systems more power-efficient into the indefinite future.

Flush from those two obvious successes, your editor went off and stated that the bulk of the realtime tree would be merged into the mainline kernel by the end of the year. Oh well. Your editor should know by now that expecting deterministic merge times for realtime patches is a sure path to disappointment; latencies in this area are always higher than one would like. In this case, the realtime developers got stuck in a high-priority interrupt (taking over the x86 architecture) with the result that realtime work got preempted and suffered from severe starvation.

As predicted, debate over Microsoft's OOXML format continued, and Microsoft succeeded in obtaining standard status for that format anyway. Things have since gotten quieter, though, perhaps because people see it as a done deal and no longer worth fighting about.

The GPL was the subject of two predictions this year. One was that more projects, perhaps even glibc, would move to GPLv3. There is a steady stream of analyst verbiage to the effect that GPLv3 is quickly growing in popularity (example), but the truth of the matter is that the number of conversions in projects which really matter appears to be low. Projects with significant numbers of developers and users continue to approach GPLv3 with caution.

The other prediction was that GPL enforcement actions would continue, and perhaps grow. The recent FSF lawsuit against Cisco makes it clear that the GPL enforcers are serious about what they are doing. Your editor cannot help but wonder, though, whether the increasingly litigious actions by the Software Freedom Law Center might not eventually lead to a serious backlash within the community. We are about freedom, not punitive damages. Enforcement of the GPL is necessary if we expect our licenses to be taken seriously, but overly zealous - or greedy - litigation could encourage those who say that use of free software exposes companies to an unacceptable level of risk.

Your editor included a rosy prediction about the One Laptop Per Child project and where it would go over the course of the year. In fact, OLPC has continued to work toward its goal of putting laptops into the hands of children around the world. But your editor completely missed the way internal divisions would rise to the surface and distract OLPC developers from what they are trying to do. OLPC seems to have moved beyond the worst of that, and much-needed development on the Sugar software continues. But the project seems far from its original goals, and the increasing popularity of ultra-mobile systems, while vindicating the original vision behind the OLPC hardware, threatens to render the XO hardware obsolete and irrelevant.

Ever the optimist, your editor said that the days of hardware hassles would be over. We are closer. Finding an off-the-shelf system - server, desktop, laptop, or palmtop - which is fully supported by Linux is now easily done. OK, maybe the modem is not supported, but few people will be inconvenienced by that omission anymore. That said, there will probably never be a shortage of uncooperative hardware manufacturers; if we value our free operating system, we must continue to support manufacturers who work with our community, and avoid those which do not.

The prediction that the intensity of competition between distributors would increase was reasonably well satisfied. One need only look at Novell's "migrate from Red Hat" offering or the continued attacks on Ubuntu, not all of which have to do with its community participation.

Finally, the three "community" predictions at the end of last January's article were all satisfied reasonably well. None of them were especially daring, so that should not be surprising.

What was not predicted

One commenter in January asked about the lack of predictions about SCO. In December, it is hard to say that SCO deserved a place there. The company still exists in some form, but it no longer has much to warrant the attention of the Linux community. Your editor predicts that there will be no SCO predictions in 2009 either.

So what else did your editor miss? Perhaps at the top of the list is the evolution of the Linux platform as it is used in mobile devices, and in cellular telephones in particular. Google's (unpredicted by your editor) Android platform has made a splash, regardless of what one might think of its openness. The first Android phone has been reasonably well received, and it would appear that more are on the way. The merger of the LiPS and LIMO consortia shows that some consolidation is happening in this area. The announced plans to open Symbian were also an interesting development. In the near future, the handset business seems likely to be firmly dominated by free software - though, alas, the bulk of those handsets will not be designed to pass the benefits of that freedom on to their owners.

Your editor has often predicted software patent troubles, though he did not do so in 2008. What was completely unforeseen, though, was Red Hat's resolution with Firestar Software. The company got itself out of a patent bind, and, in the process, removed the patent as a threat to the wider development and user community too. We may see this sort of solution repeated for patent problems in the future - if we are lucky.

Finally, unpredicted - and unpredictable - was the series of "infrastructure issues" which shut down much of the Fedora project for a good month. That episode showed us a number of things: how much some of us depend on our distributors' infrastructure, how vulnerable we can be to intrusions, and how the interests of the companies behind some distributions can interfere with the availability of useful information. Months after the fact, we still have no idea what happened with the Fedora project; it is not unreasonable to wonder if we will ever know.

Despite problems like that, and other small distractions (the total meltdown of the global financial system, for example), Linux has only grown stronger over the last year. Our community has grown, our software has gotten better, and the economy around free software has gotten stronger. Your editor predicted that, too, but not even he is so arrogant as to claim credit for having foreseen something nearly as obvious as the sunrise.


(Log in to post comments)

The Grumpy Editor's 2008 retrospective

Posted Dec 24, 2008 14:35 UTC (Wed) by robertknight (subscriber, #42536) [Link]

> Oh well. Your editor should know by now that expecting
> deterministic merge times for realtime patches is a sure
> path to disappointment

That made my day - cheers Jonathan :)

The Grumpy Editor's 2008 retrospective

Posted Dec 24, 2008 17:57 UTC (Wed) by jengelh (subscriber, #33263) [Link]

>deterministic merge times

Trying to apply rt patches whilst relying on them for the submission process is like a perpetuum mobile. :D

The Grumpy Editor's 2008 retrospective

Posted Dec 24, 2008 18:47 UTC (Wed) by jospoortvliet (subscriber, #33164) [Link]

Yeah, I thoroughly enjoyed that paragraph...

The Grumpy Editor's 2008 retrospective

Posted Dec 27, 2008 0:00 UTC (Sat) by sbergman27 (guest, #10767) [Link]

...
and how the interests of the companies behind some distributions can interfere with the availability of useful information. Months after the fact, we still have no idea what happened with the Fedora project; it is not unreasonable to wonder if we will ever know.
...

Oh, I suspect that if we keep asking and asking, and don't just let the issue die, as some are counting upon it to do, more of the truth will eventually have to be revealed.

Lawsuit Backlash

Posted Dec 27, 2008 6:16 UTC (Sat) by ldo (subscriber, #40946) [Link]

Your editor cannot help but wonder, though, whether the increasingly litigious actions by the Software Freedom Law Center might not eventually lead to a serious backlash within the community.

To those looking at comparisons with, say, lawsuits by the RIAA/MPAA, it's worth noting that GPL lawsuits target not the users of the licensed software, but those who redistribute it. In other words, they're not suing the actual customers for the software, only those who are out to rip off the customers. I think this should be enough to forestall any kind of bad feeling against the lawsuits--they're only being filed against those who are trying to make a profit out of this software without fulfilling their reciprocal obligations, and for whom nobody should be feeling any sympathy.

Lawsuit Backlash

Posted Jan 9, 2009 18:57 UTC (Fri) by pimlottc (guest, #44833) [Link]

I think the concern is more that companies will see using open-source within their own projects and products will be more hesitant to do so if there is a perception that it opens them up to possible legal liability.

The Grumpy Editor's 2008 retrospective

Posted Dec 27, 2008 17:37 UTC (Sat) by bronson (subscriber, #4806) [Link]

I think the editor is right about the danger of the olpc being obsolete. I bought a g1g1 to be a teaching toy for my niece and to read rss feeds in bed. Sugar's UI taught my niece more about computers than I intended (can't figure out how to save her work to a usb key, can't print it, can't email it, it's locked inside the olpc forever), and its horrid battery life and glacial boot times prevented use as an rss reader.

My niece is now a proficient Mac user and I read feeds on my G1 (typing on it now). The olpc has sat idle on the dusty shelf for a year now... I'm not quite sure what to do with it. :-/

The Grumpy Editor's 2008 retrospective

Posted Dec 27, 2008 20:32 UTC (Sat) by dlang (✭ supporter ✭, #313) [Link]

to copy things off of the olpc plug in a USB stick, go to the journal, select a document, hit copy, select the USB stick (at the bottom of the screen), select paste.

as far as printing goes, that is still a problem (although scheduled to be fixed in the march software update, at least to some extent)

you need to differentiate between teh hardware becoming obsolete and the horible problems the software has (not as bad as it used to be, but still pretty bad)

the good news is that you can now run other linux distros on the olpc, so you aren't locked in to Sugar.

there are how-to documents for installing ubunto, debian, gentoo and fedora on the machine, so you can choose your favorite flavor

The Grumpy Editor's 2008 retrospective

Posted Dec 28, 2008 16:31 UTC (Sun) by vonbrand (subscriber, #4458) [Link]

Sugar is available as a set of Fedora packages (at least in rawhide). So you could hop in and help make it better.

The Grumpy Editor's 2008 retrospective

Posted Dec 28, 2008 16:59 UTC (Sun) by dlang (✭ supporter ✭, #313) [Link]

you really should not attack people on your side (at least partially).

I was responding to a post that voiced the opinion that the XO is becoming obsolete (and listed many Sugar problems as justification). this is a person who went out of their way to conribute by spending their hard earned money to pay double price for a device.

your response annoys people the same way that a bug report that's responded with a message that says 'patches are welcome' annoys people

attacking people who contribute becouse you don't think that they contribute enough (or in the 'right way') harms the community for more than it ever helps.

I have purchased 6 XOs through the G1G1 program (two for my own use/testing, four for relatives), I do contribute (via testing)

however, that's not necessarily the important point.

the OLPC people decided to deploy a system that is in many ways unusable (for the reasons that were in the message I replied to), and they made it worse by doing so in a way that made it very hard to use any of the standard tools. they then push the result as the most user friendly version ever.

while I test Sugar (on the stripped down Fedora shipped with the OLPC) I think that this combination is a big mistake, and I'm not interested in spending a lot of time trying to convince Fedora to change when there are other distros that give me a much better starting point, so I spend more time working with the other distros that I can run on the XO.

OLPC Sugar problems

Posted Dec 28, 2008 17:29 UTC (Sun) by vonbrand (subscriber, #4458) [Link]

Sorry if it sounded that way. I was just trying to point out to other readers here that interested parties can help out with the interface without owning an OPLC themselves.

OLPC Sugar problems

Posted Dec 29, 2008 0:50 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]

sorry for taking your comment in ways you didn't intend. I just have had too many times when a discussion of tools has gone

person 1: X has these problems try using Y

person 2: why don't you contribute code to fix X instead

sometimes the right answer isn't to work on product X to 'fix' it (in some cases the 'fix' is in direct conflict with the goals of project X), but to just switch to a different option

The Grumpy Editor's 2008 retrospective

Posted Dec 29, 2008 17:15 UTC (Mon) by bronson (subscriber, #4806) [Link]

> I spend more time working with the other distros that I can run on the XO.

Now this is interesting. What distro do you find to be the most usable? Is there anything that will sleep when the laptop is closed, doesn't burn through the battery in an hour, lives agreeably in flash, and only takes an hour or so of my time to install and configure?

In reply to vonbrand, I'm personally uninterested in contributing to Sugar. It feels slow, incomplete, and poorly designed. And I disagree with its claim that existing UIs are so broken that the baby must be chucked out with the bathwater. If it had started as a set of extensions to a tried and true desktop environment (unimportant which one), I feel the XO would have been generally usable by now and the whole project would have seen far more momentum. Alas.

The Grumpy Editor's 2008 retrospective

Posted Dec 29, 2008 17:56 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]

I'm mostly running them from USB sticks at the moment (since I'm experimenting with several options)

that being said, I have had the best results so far with the debxo images (debian)

I expect the ubuntu option to work about as well, but the one image I tried didn't want to work from the USB (looks like a bootloader being hard-coded for the SD card slot, but I haven't tried it yet)

all the debian options and the ubuntu option are small enough to fit in the built-in flash (unlike the fedora 10 image)

none of these do power management well yet, the problem is that the OLPC team went their own way (again) and instead of teaching the kernel about the power management options they created a userspace tool that accesses the hardware directly to do the power management. until this gets fixed (which _is_ on a short-term roadmap) it's just about impossible to do power management properly without running the full olpc distro. I see battery life in the 2-3 hour range with no power savings.

but things are changing rapidly, a month or so ago none of these distros was able to access the game keys on the screen, or control the screen brightness and mode. at this point I believe that the XO can run a kernel compiled from raw kernel.org sources (also not possible a few months ago)

it's hit the point where the various options can be used, so more people are trying them, each doing small tweaks to fix things and the results are getting combined.

Sugar is so slow that KDE and Gnome both seem fast by comparison. I don't have enough experiance with LXDE or Awesome to really use them, but they are considerably smaller (and should be faster)

The Grumpy Editor's 2008 retrospective

Posted Jan 8, 2009 6:34 UTC (Thu) by az (guest, #46701) [Link]

Your editor should know by now that expecting deterministic merge times for realtime patches is a sure path to disappointment; latencies in this area are always higher than one would like. In this case, the realtime developers got stuck in a high-priority interrupt (taking over the x86 architecture) with the result that realtime work got preempted and suffered from severe starvation.

*stabs Jonathan*

Flash Legal Issues

Posted Jan 9, 2009 4:05 UTC (Fri) by jrincayc (guest, #29129) [Link]

>But support for many other Flash features, including audio and simple playback from online sites, still is not especially solid, and other interactive Flash applications do not work at all.

Of course flash support for audio and video is not particularly good for many sites, since legally, in the US and other countries with software patents, it cannot be distributed without a license for the relevant codecs. For example, youtube uses MP3 for the audio and H.263 for the video. Both those have unexpired patents, so free software for displaying youtube videos is legally problematic in the US and other countries where software patent exist. Until the patents are either invalidated or expire, or the companies grant royalty free permission, this problem will exist. The possibility of getting sued tends to decrease the number of programmers who will work on a project.

http://www.itu.int/ipr/IPRSearch.aspx?iprtype=PS
http://scratchpad.wikia.com/wiki/MPEG_patent_lists
http://en.wikipedia.org/wiki/Youtube#Format_and_quality_c...

The Grumpy Editor's 2008 retrospective

Posted Jan 13, 2009 20:14 UTC (Tue) by pboddie (subscriber, #50784) [Link]

Enforcement of the GPL is necessary if we expect our licenses to be taken seriously, but overly zealous - or greedy - litigation could encourage those who say that use of free software exposes companies to an unacceptable level of risk.

How is legal action against Cisco or any of the other persistent infringers "zealous"? As far as exposure to risk is concerned, it's shocking how businesses pretend to be all "professional" (whilst portraying the Free Software community as "hobbyists"), have a bunch of lawyers ready to litigate at a moment's notice, and yet seem unable to read and understand common software licences. But then again, the fashion in big business today seems to be about paying scant attention to regulations, knowing that saying "sorry" in the least insincere way possible when caught doing something wrong will probably get you off the hook.

If 2008 had any major lessons to offer, one of them would surely be that the public, typically overridden and manipulated by big business, occasionally demand that corporate interests be brought to account for their behaviour. The FSF and SFLC, typically constructive in their efforts to resolve licensing problems, shouldn't need to apologise for their litigation efforts: they're only bringing to book those corporate entities who, despite reasonable attempts at persuasion, still believe that anything which isn't nailed down by a guy with a private jet and a large legal department is just there for the taking.

Copyright © 2008, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds