Raymond also scorned the idea that Microsoft's code would be desirable -- although he did predict that open-source hackers "would descend on that source like a horde of locusts, find all the closed protocols that they are using to ensure 'lock-in' and we would then write that into Linux and never look back."

But Raymond doesn't want that advantage.

"I want to see them taken down but I want the market to do it, not the government," says Raymond. "I have no argument with this finding of fact -- Microsoft does have monopoly power, it does engage in sleazy business practices and there are many thing that people should loathe about it. But I fear a government with the power to punish these crimes more than I do the so-called crimes themselves."

Raymond's viewpoint is representative of that of a healthy proportion of open-source programmers. But does it take into account some of the factors that have nurtured the growth of open-source software? A case can be made that open-source software, monopoly power and the government have actually been interrelated for quite some time, in an intriguingly unexpected fashion.

In 1956, another federal judge, Thomas F. Meaney, enjoined AT&T under a consent decree that forbade the telephone monopoly "from commencing ... manufacture for sale or lease any equipment [other than that used in providing telephone or telegraph services]." Judge Meaney also required AT&T to reveal what patents it held and to supply information about them to potential competitors. As a direct result, says Unix historian Peter Salus, years later, when enterprising Bell Labs researchers invented the Unix operating system, AT&T's lawyers forbade the company from attempting to market the operating system commercially. Instead, AT&T licensed Unix to universities and research laboratories at a nominal cost.

(However, in what may end up as one of the great ironic moments in software history, Salus notes that the eventual use of Unix as the operating system most suitable for networking computers together over phone lines means that Unix actually could have been considered equipment that fell under the rubric of AT&T's main telephony business.)

According to Salus, the terms of the consent decree "resulted in a much more rapid dissemination of technology than would otherwise have been possible." Computer researchers, most prominently at the University of California at Berkeley, improved Unix constantly, adding features and fixing bugs -- and putting in place the template for how all free software/open-source software projects have proceeded since.

Raymond disputes this view of computing history, arguing that AT&T had never intended to commercialize Unix in the first place, that it had always thought of Unix as something to be shared with other researchers. And O'Reilly notes that in 1982, the government-mandated breakup of AT&T -- which permitted the phone company to compete in non-telephony markets -- had another paradoxical effect on open-source development. Once AT&T was allowed to enter computing markets, it attempted to clamp down on the academics who were still busy working on descendants of Unix -- most notably the various BSD variants. The adverse legal atmosphere drove developers away from BSD, suggests O'Reilly, and may be one of the main reasons why Linux achieved such sudden widespread developer support.

It would be incorrect to claim that government action gave birth to open-source software, or to Linux -- certainly the concept of sharing source code was widely practiced even before Unix came along. But it can be argued that the 1956 consent decree gave Unix and open source-style development a huge boost, and that the 1982 AT&T breakup also had an impact on the software marketplace.

Should the government step in again? It now seems undeniable that it will attempt to do so. But Judge Jackson should step carefully. History indicates that there is precedent for taking action that will have clear impact on the world of open-source development -- but usually in unintended and unpredictable forms. The war cry of trust-busters used to be "Break up the monopoly." In today's software marketplace, the new call to arms may be "Open up the code."

Recent Stories

Ask the pilot
The gut-churning trials and tribulations of making the grade with an airline.
Ask the pilot
Who cares what planes look like? I do! Why do they have to look so ugly and boring?
Ask the pilot
Avoiding speculation, the pilot weighs in on the Madrid plane crash.
Ask the pilot
What do U.S. carriers need to do to regain their status as world-class players? Wi-Fi would help.
Ask the Pilot
The safe landing of the damaged Qantas 747 was no miracle. Plus: If a plane loses pressure, will your eyes pop out?

Daily Newsletter

Get Salon in your mailbox!