Home | About | Search | Archives

Free as in Freedom - Part Two: New Linux
Press Action
Sunday, December 12, 2004
http://www.pressaction.com/news/weblog/full_article/engel12122004/

By Adam Engel

"A frightening array, and seemingly endless. Vaccines created to make people sick, radioactive ammunition designed to sicken and kill our own troops, chemtrails that have left half the country stricken with a debilitating bronchitis that never goes away, the destruction of our Constitution by cynical Congressional fiat, a plan to put all our schoolchildren on prescription drugs the ingredients and consequences of which are never fully revealed until it’s too late, our brains shredded by microwaves from cellphones, the never-ending robbery of our treasury by Israelis to support their genocide of the people whose land they stole, and the sinister plot by corporate giant Monsanto to kill half the world by starvation with bioengineered seeds that produce sterile crops .... the list of horrors inflicted upon us by corporate criminals does not end. “
-John Kaminski, “The Mirage of the Miracle"

[Note: All dialog is culled from email conversations unless otherwise noted. -AE].

Perhaps I was over-zealous in my praise of Richard Stallman and the Free Software Foundation (FSF) in Part One of this article, “Free as in Freedom: GNU/Linux.” That would be unfair to many major corporations and the state of the world they’ve created. Lots of people, especially “successful” Americans, like the world just the way it is. Oh well. It was a history of “GNU beginnings,” the start of a movement that, unlike anything we’ve thus far seen, said “No!” to the corporate-defined order and created an alternative to corporate rule by “copyright,” and an operating system that challenged the way certain corporate monopolies have defined our desktops and how we use them (or go directly to jail).

Well, that was last week’s article, which focused on GNU/Linux. Old. Old. All that progressive, anti-corporate stuff is ridiculous, romantic nonsense anyway, at least according to Eric Raymond, author of “The Cathedral and the Bazaar,” and co-creator (along with various user/collaborators) of the immortal fetchmail program. This article is going to focus not on GNU/Linux, but “New Linux,” the operating system as it exists today, with GUI desktop environments and all the features of your favorite monopoly software (plus thousands of Unix-like programs, tools, utilities etc.). So, time to wrest that sword-helmet-cuirass combo from Richard Stallman—though he did look awful good in that garb—and place them on the person of Raymond’s visionary of the now-and- next-week, the one and only Linus Torvalds.

Also, despite the legitimate concerns of the Free Software Foundation, the operating system will never be called GNU/Linux, just “Linux.” This could be for brevity’s sake, or because the idea of GNU/Linux was promoted too late, or other reasons only we paranoid progressives—actually, I’m not a progressive; I’m an anarchist, but it’s all the same “lefty crowd” (except for Libertarians who manage to “pass” for conservatives or plain old folks) of whiners and discontents, the kind of folks who fail to appreciate all the great stuff corporate monopolies bring to what’s left of life on earth.

I began this article or series of articles because I saw in GNU/Linux an example of a successful rebellion for “the left” to examine as a model. I don’t think I was mistaken, though, as with all movements, once the “revolutionaries” have set the ground, the “liberals” take over and try not only to remake the present, but rewrite the past. If I “lionized” Stallman and “romanticized” GNU and the free software movement to create a “founding” myth—oops. Better the real revolutionary Jefferson than the paper and wax model we have today thanks to generations of post-revolutionary revisionists. Stallman and the FSF did what I said they did, despite my zealous praise, which is why GNU/Linux exists today.

I was fortunate to have found the perfect guide for my journey through the Linux past and present, the politics of Linux: Ben Okopnik, Editor-in-Chief of the Linux Gazette. Yoga instructor and practitioner, Unix instructor and practitioner, writer, editor and Linux aficionado, Ben was both open to new ideas, familiar with “old” ones, and willing and able to point me in the various directions I needed to go to “explain the GNU/Linux model” to mostly non-technical “left” and “progressive” readers.

“Linux is inextricably political—and deliberately so, from its very inception. The OS itself is a tool, as sharp, bright, and beautiful as it may be; creating a better world, in which human beings cooperate rather than fight each other ‘to achieve the same exact ends’ is, from my perspective, the goal,” wrote Okopnik.

It was Okopnik who urged me to publish this article under a GPL-like license and pointed me to the website where this could be done in minutes.

“Please consider releasing this interview under the Open Publication License (the OPL is available at http://www.opencontent.org/openpub/), or something similar. It’s not a condition of the interview, but I’d strongly prefer it. This license respects your commercial rights and can be “adjusted” to suit your exact purposes; it’s the license under which all Linux Gazette (LG) articles are published,” he wrote. “If you release this interview under the OPL, you can define whatever restrictions on distribution you choose; as an example, Cory Doctorow, an excellent and highly-popular writer (see http://craphound.com/) recently released several of his books under the OPL. He talks about his experience on the site, and as a result of that experience has actually eased off on the restrictions he originally imposed. Nor is he the first by far; take a look at, e.g., MIT’s OpenCourseWare site: http://ocw.mit.edu/index.html (Good resource to bookmark in any case.)”

“In order to license this article, I just have to declare it?” I asked.

“Yep,” wrote Ben. “Do a run-through of the “wizard” at http://creativecommons.org/license/ to make sure that you have exactly the license you want—it only takes a few seconds—and it’ll generate the legal notice you need. Nice and neat.”

“I don’t have to apply to anyone for approval?”

“Nope; you’re The Boss when it comes to licensing your own stuff. Isn’t that nice?” Ben wrote.

Ben also gave me another perspective on the GNU revolution and its major and minor aspects. For instance, the FSF’s insistence on calling “Linux” GNU/Linux, though valid, violates the peoples’ tendency to abbreviate (hence the many abbreviations and acronyms in the Unix/Linux operating systems themselves), and according to Software Developer and Systems Designer Paul Ford (author of the phenomenal Ftrain - http://www.ftrain.com - website), the GNU/ prefix came too late in the game. All the “Linux” books and CDs had gone to print; the word “Linux” came to mean both the kernel and operating system, though Linus Torvalds and supporters, developed the kernel and GNU the other essentials of the OS.

“Note that this distinction, much as RMS (Richard M. Stallman) and others may have tried to promote it, did not make it into the common lexicon. Just as in the case of the ‘X Window System,’ universally known as ‘X,’ a short simple identifier is what people will use when it’s available. As an example, looking through my 55 MB ‘sent mail’ archive (gads, but I do a lot of writing!), I find myself using the term ‘GNU/Linux’ exactly once, back in 2000,” wrote Okopnik.

“Everyone I know calls it ‘Linux.’ Everyone appreciates Richard Stallman’s extraordinary contributions. He’s a genius, and has a MacArthur genius grant to prove it. But the ‘GNU/’ prefix was added a few years too late. I’ll call it GNU/Linux in writing, sometimes, though. Honestly, I don’t care what people call it. That entire debate seemed anathema to the open source ethos, too similar to someone protecting their registered trademark,” Ford commented.

Regardless of what it’s called—I’ll call it GNU/Linux out of respect for its GNU origins—GNU/Linux is a political phenomenon, the creation of user/developers for its own sake. Or rather, for their sake. Rather than succumb to the Microsoft Monopoly, which places Windows on virtually every PC sold in America, they created their own free system and licensed it not for the benefit of an elite few, but for anyone with the capability to alter the code.

Okopnik describes the “typical” Linux user thus:

“I don’t want to idealize Linuxers in my answers; none of us humans are perfect saints, and the wild bunch who cleave to this OS and this community are little different in that respect. However, just as exaggeration in teaching is used to emphasize a point, isolating or highlighting the common trends and traits in this case can provide an interesting introduction. Keeping that in mind:

KDE and GNOME: Linux for The Rest of Us

“I first came to Linux in 1996, when it was already a world-wide phenomenon, but still a ‘techie/hacker’ thing. I was on the command-line for six months before I installed X-windows; nevertheless, I was surprised at the number of alternatives a Unix-type system gave me, especially as a writer in terms of text formatting and manipulation etc. Emacs, vi and though I didn’t get into Tex or nroff, I used Applixware, once it came out. to do the formatting one does in Windows. Because of various jobs I took as both a free-lance and cubicle-bound ad-man and copywriter, I had to install Windows and gradually moved away from Linux for about four years. When I came back to it with SuSE 9.0 in December of 2003 I was astonished. KDE, (KDE.org free desktop environment), GNOME (GNU’s free desktop environment), Open Office (OpenOffice.org’s free office suite), the whole new GUI interface floored me,” I wrote Okopnik.

“This is not an uncommon reaction in this venue,” wrote Okopnik. “The rates of growth and development in Linux are simply phenomenal—and still accelerating.”

“Essentially ‘every school’ in India runs Linux. Same for South Africa. France has passed a law that says ‘Open Source is to be implemented whenever possible’; Brazil, which was ~8% of Microsoft’s business a couple of years ago, has followed suit. Germany has been using Linux in their security departments, and is now implementing it at every level—federal, state, and local. China has decided that it’s their official OS; Korea and Japan have joined them in investing several billion dollars in FLOSS software development recently. Most of South America is switching, led by Peru (Dr. Villanueva Nunez, a Congressman, responded succinctly and brilliantly to the fear-and-doubt tactics that Microsoft tried to sow when the decision was made; the translation can be found in many places on the Net.) This is just off the top of my head; there are many other countries which have decided that FLOSS simply works for them (generally by making them competitive in the world market and removing an unnecessary barrier to their pool of talented but poor would-be techies.)”

“What’s FLOSS?” I asked.

“An unwieldy compromise of a name that the majority can live with. As you’ve probably figured from your exchange with Stallman, there’s some disagreement about exactly what this whole movement should be called—and Free/Libre/Open Source Software is what we got as a result. Like dead yeast in beer, it’s harmless and doesn’t even affect the flavor,” wrote Okopnik.

“Once money is not the primary motivator, a number of interesting results show up. FLOSS is a social experiment gone successful—mainstream—wild, a meritocracy/gift-based culture that focuses on exchanging people’s best abilities for community recognition and respect. Part of the secret of its effectiveness is that you can’t cheat people out of respect the way you can with money—it can always be lost or withdrawn. Like any other human system, it has its imperfections (see Cory Doctorow’s “Down and Out in the Magic Kingdom” or James P. Hogan’s “Voyage into Yesteryear”, both of which describe a respect-based system as the basis of an economy), but they’re a) usually self-correcting and b) several orders of magnitude less extreme at the edges than what we have now,” wrote Okopnik.

I wrote to Okopnik, “KDE and GNOME, especially KDE 3.1x, worked as well as or better than the Win2000 I had installed four years ago, and I’ve yet to experience a full crash—that’s par for the daily use of Windows 2000. More significantly, I was turned onto ‘the New Linux’ by someone who knew about as much about the Unix command-line as the typical Windows user knows about DOS. Similarly, I turned someone else who was sick of Microsoft’s shoddy but expensive products to the mind-boggling array of free software programs that run under Linux, though he had neither the time nor the inclination to learn about the operating system. Like many users, all he wanted and needed was a word-processor, a browser, a mail program, some games, and as little trouble as possible. SuSE 9.0 provided him with all of these things, and now, after a year on Linux, he knows slightly more about the Linux command line than he did it’s retarded younger brother, DOS. Have you noticed more of an interest in Linux or an enhanced readership since Linux became both market and user friendly? If so, are these new users less interested in the ‘technical’ aspects than in having a stable GUI-based system to for work and email and net-surfing?”

Okopnik responded, “Actually, this is an issue that I brought up in an involved discussion with the LG staff and the Answer Gangsters (The Answer Gang answers Linux questions sent to us by our readers, and the discussions and the answers become part of LG.) My viewpoint here is that it’s actually a very good thing—modulo the awareness that the Command Line (CLI) exists. That is, people are perfectly welcome to come to Linux and use only its GUI capabilities as long as this serves their needs—but when the GUI proves insufficient, the capabilities of the CLI are there, just underneath, providing the perfect security blanket.

“In an article I wrote for Java Developers Journal, I related an example of this. I had a client whose Web developer left them in the lurch with several hundred HTML files without the ‘.html’ extensions. This wouldn’t be too bad by itself—renaming a group of files isn’t difficult—but the thousands of HTML links within the files referred to those extension-less names as well. With GUI-only tools, this is a nearly-unsolvable disaster. From the CLI, it was a matter of a single short line of code.

”The readership of the Linux Gazette (LG) has certainly changed over time. Where we used to get dozens of questions on fairly technical topics in The Answer Gang, we now get only a few—and they tend to be simpler, less technical. The email I get from our readers indicates that there has indeed been a definite shift in the user base; the old Linuxer who would bang on a problem for hours so that it could be reported (and quickly fixed) is being… well, not replaced, but reduced, percentage-wise, as the mainstay of the population. The new user is often just that—a computer user who just wants that email/web/document/spreadsheet processor and maybe a few games on the side. There is, however, a cultural shift that occurs even in those users after a while: you cannot live in a society based on a given moral premise and ignore that premise, or even stop it from penetrating into your life (even if you try to prevent it.) The original “hacker ethic” of Linux lives on, strong as ever in those who use the full extent of this OS, and inherent (and growing, however slowly) in those who use it even without that full knowledge.

Paul Ford wrote, “I used to think there was too much emphasis in the community on ‘claiming the desktop,’ trying to compete with Windows, but the latest GNOME is attractive and elegant, and works great, looks as good as MacOS X, and doesn’t feel like a thin skin over Unix at all. It’s an environment I could use every day. So I was wrong--the desktop was a good aim, it just took a while to get things to a good point.’”

According to George Staikos, a KDE developer and spokesperson, “The KDE project was formed by a small group of computer programmers and Linux and UNIX users who were fed up with the lousy state of user interfaces available for their operating systems. They wanted something that was fast, powerful, featureful, and looked good. Notice that making money was not one of the requirements. They set out to accomplish this task in the most effective manner possible, which was to use the Qt toolkit (at the time distributed free of charge for non-commercial use under a restrictive license, but now distributed under the free GPL license for non-commercial use). Because there were very many people around the world with similar desires and compatible skills, because there was no risk of someone hijacking the project and turning it into a business, and because there was actually proof-of-concept working code already being produced, the project quickly grew. After a few years, the core of the system was very solid and new programmers could easily find a niche to work in, implementing that feature they always wanted or fixing that bug that has bothered them for so long. These individuals are what makes KDE work. They keep the project evolving, bringing new ideas and new manpower. There is relatively no risk involved in contributing, and the rewards are plenty. Developers (including coders, translators, documenters, artists, and more) can contribute whatever they have time for.

“Of course there are other requirements to keeping such a project going. We need bandwidth, servers, funds for promotion and travel, and more. This tends to come from corporate users who are kind enough to contribute back to ensure the progress of the project, and from home users who perhaps can’t contribute in other ways. Some people also contribute system administration time. This is all very vital to the success of KDE.

“It’s important to note, however, that KDE is indeed paid for, as much as any other software is. KDE is paid for by individuals, and paid for in a distributed manner. Our time, as KDE developers, is worth as much money as any other software developer (More, if you ask me. KDE developers tend to be one smart bunch!). KDE is indeed a very costly project, and is paid for by society itself, as much as a result of the lack of momentum of the commercial sector to create a useful solution to existing problems.

“What is KDE ‘worth’? The freely available SLOCCount tool gives me an estimate of $22.6 million just for the KDE libraries alone, a small fraction of what is KDE. Most of the code in the KDE libraries was developed from 1999 through 2004, almost 6 years in total. Not including the Qt toolkit, KDE must be worth well over $250 million. This also doesn’t include artwork, documentation and language translations, which KDE is well known for.

Total Physical Source Lines of Code (SLOC) = 608,228
Development Effort Estimate, Person-Years (Person-Months) = 167.61
(2,011.32)
(Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05))
Schedule Estimate, Years (Months) = 3.75 (45.01)
(Basic COCOMO model, Months = 2.5 * (person-months**0.38))
Estimated Average Number of Developers (Effort/Schedule) = 44.69
Total Estimated Cost to Develop = $ 22,641,821
(average salary = $56,286/year, overhead = 2.40)

[the above data was generated using David A. Wheeler’s ‘SLOCCount’ tool]

I wrote, “Was KDE originally supposed to be free-ware? I remember when I first saw the specs in the mid-late nineties, I thought it seemed too good to believe. Yet it’s here and working and continues to grow in functionality and popularity. In fact, the SuSE 9.x package uses KDE as its Graphic base. Can this go on without some serious cash flow?”

Staikos wrote, “Yes, KDE was definitely supposed to be free, both in cost, and in terms of speech. KDE was to be available free of cost to all, and available for modification and learning as desired as long as it was not abused for commercial gain by others who weren’t interested in contributing back. That is to say, the licensing prohibits using KDE code in a non-free project, though you may use KDE for that project. For example, you cannot copy source code from KDE and embed it in your commercial, closed-source application. The KDE license actually requires you to release the source for your application as well. However, you may make calls to the KDE libraries from your application. In short, free to use, yes, free to steal from, no.

“Indeed KDE is growing rapidly in popularity. We do need to find new ways to support the project in terms of getting the hardware we need, the administration help we need, the legal work done, and paying for conferences and developer meetings. It’s an ongoing struggle.

“Making money is not a bad thing, and I think making money off of KDE is a good thing for KDE. Stealing code from KDE is however not a good thing, and that’s what the GPL protects us from. Most of KDE is licensed under the GPL, while the libraries tend to use the LGPL in order to permit commercial KDE applications to be developed. Some portions of KDE are under more liberal licenses such as the Berkeley Software Development (BSD) license because the author did not have concerns with others using that code in non-free software. KDE as a project maintains that our software must be compatible with the GPL, but it need not be specifically licensed under the GPL,” wrote Staikos.

I wrote, “I know several people who, finally fed up with Windows, and not wanting to deal with getting a new Mac, switched over to Linux even though they know only the rudiments of command line arguments and don’t plan on learning much more. Like many users, all they use their computers for is word-processing, presentations, a web browser and email. Since the advent of KDE and GNOME, people can use Linux the way they use Mac or Windows without spending the time and effort necessary to learn a Unix-like OS. This would have been unthinkable a few years back, even with relatively user-friendly Window Managers like Windowmaker and IceWM. One of the people I’m interviewing for this article, the editor of the Linux Gazette, confirmed this ‘trend’. More and more of his readers are concerned with ‘typical’ user issues rather than the more technical aspects of Linux. Do you think that with the advent of GUI-based Desktop Environments such as KDE that Linux will appeal to a wider audience who want a choice other than Mac or Windows?”

Staikos wrote, “Most definitely. This was the original goal of KDE, and still remains one. However KDE does not have the resources to provide a real end-user system. We only ‘ship’ source code, and it is up to the distributors to set their preferred configuration defaults, customize the menus, and determine which applications to add or remove. These things are absolutely vital to creating a valuable end-user experience, and in fact are different for each target market. I think Linux with KDE is already a perfectly suitable solution for the average desktop system. The obstacles in place are more monopolistic in nature. Users are accustomed to the way MS Windows works. They learned this over many years, and expect that all computers work this way, even if it’s inefficient or poorly designed. They’re impatient to learn a new system, and balk at the idea of using Linux. Furthermore, most commercial applications are designed only for MS Windows. It’s hard to justify using Linux when your favorite video game or other software only runs on Windows. Hopefully we will change this over time, as KDE becomes more popular and software developers can justify porting to Linux.

“I think KDE is one of the driving factors that is pushing Linux into the mainstream, and I do hope that it will one day be a serious competitor in terms of user base to MS Windows. The world needs an alternative, and Linux is here to provide it,” wrote Staikos.

While GNU/Linux is “inextricably political,” both Ford and Okopnik admit that most users are less into the politics than the practical applications of the system itself.

Ford wrote, “Linux has a pretty amazing advantage in that you get something for free, or a very low cost, out of the movement. It’s hard for any movement based on ideas to compete with that—it’s not like you can say, ‘if you buy into Noam Chomsky’s theory of foreign policy, we’ll give you a free Chomsky hat.’ Whereas Linux can say, ‘if you’re willing to believe that Open Sourced software works, we’ll give you a free operating system with all the trimmings and cranberry sauce.’ So the two ‘movements’ don’t really compare.”

While for the Stallman and the FSF the difference between the “free” and “open source” movements is significant, for Ford they are pretty much the same.

“I think they’re usually interchangeable,” Ford wrote. “And in truth, I don’t really care that much. If a license is similar to the GPL, I’ll go with it. For things like OCR or image editing, I don’t mind buying commercial tools. They tend to be in much better shape than their open-sourced counterparts. They’re very task-based—I’m scanning a page, or creating an image. If good replacement software comes along, I’ll use that. But in the meantime, the work is done—I’ve got my output....But for any programming project, where people need to work together, and thousands of hours go into developing code, I’m terrified of commercial software. Lock-in is terrifying....Basically, when I’m looking for a tool, I go “shopping” for the open sourced version first. Open-sourced software lets me try out a huge number of solutions to find the best one—if I don’t like one package, I can see if there’s a better one,” wrote Ford.

According to Okopnik, the allure of GNU/Linux is rooted in the moral imperative created by the FSF and Stallman, “but is not strictly about it. That’s the flexible, fun approach that gets people involved, people who would run away from a purely political approach. Most people would have a great time living in a true democracy—but that does not mean that they all want to become politicians, or involve a significant chunk of their time in running the whole shindig,” wrote Okopnik.

Okopnik pointed me to Eric S. Raymond’s “The Cathedral and the Bazaar”—http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/—for a different take on the politics of GNU/Linux, or in this case, “New Linux.”

New Myths for New Linux: Linus’s Law and the Bazaar

“Linux is subversive. Who would have thought even five years ago (1991) that a world-class operating system could coalesce as if by magic out of part-time hacking by several thousand developers scattered all over the planet, connected only by the tenuous strands of the Internet?” writes Eric S. Raymond in his essay, “The Cathedral and the Bazaar, http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/, which chronicles the creation of his popular, fetchmail program for GNU/Linux.

Raymond extols the development techniques of Linus Torvalds, main developer of the Linux kernel, as the new paradigm for software development.

“Linus Torvalds’s style of development—release early and often, delegate everything you can, be open to the point of promiscuity—came as a surprise. No quiet, reverent cathedral-building here—rather, the Linux community seemed to resemble a great babbling bazaar of differing agendas and approaches (aptly symbolized by the Linux archive sites, who’d take submissions from anyone) out of which a coherent and stable system could seemingly emerge only by a succession of miracles.” http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/

Like Okopnik, he sees Linux users as a particularly self-reliant bunch; many Linux users, he concedes, are also Linux developers. This was written in the late 1990s, before the GNOME and KDE desktop environments increased GNU/Linux’s appeal among the general public.

“Another strength of the Unix tradition, one that Linux pushes to a happy extreme, is that a lot of users are hackers too. Because source code is available, they can be effective hackers. This can be tremendously useful for shortening debugging time. Given a bit of encouragement, your users will diagnose problems, suggest fixes, and help improve the code far more quickly than you could unaided. Treating your users as co-developers is your least-hassle route to rapid code improvement and effective debugging.

“The power of this effect is easy to underestimate. In fact, pretty well all of us in the open-source world drastically underestimated how well it would scale up with number of users and against system complexity, until Linus Torvalds showed us differently.

“In fact, I think Linus’s cleverest and most consequential hack was not the construction of the Linux kernel itself, but rather his invention of the Linux development model. Linus’s open development policy was the very opposite of cathedral-building. Linux’s Internet archives were burgeoning, multiple distributions were being floated. And all of this was driven by an unheard-of frequency of core system releases.

“Linus was treating his users as co-developers in the most effective possible way:

“Release early. Release often. And listen to your customers.

“Linus’s innovation wasn’t so much in doing quick-turnaround releases incorporating lots of user feedback (something like this had been Unix-world tradition for a long time), but in scaling it up to a level of intensity that matched the complexity of what he was developing. In those early times (around 1991) it wasn’t unknown for him to release a new kernel more than once a day! Because he cultivated his base of co-developers and leveraged the Internet for collaboration harder than anyone else, this worked.

“Granted, Linus is a damn fine hacker. How many of us could engineer an entire production-quality operating system kernel from scratch? But Linux didn’t represent any awesome conceptual leap forward. Linus is not (or at least, not yet) an innovative genius of design in the way that, say, Richard Stallman or James Gosling (of NeWS and Java) are. Rather, Linus seems to me to be a genius of engineering and implementation, with a sixth sense for avoiding bugs and development dead-ends and a true knack for finding the minimum-effort path from point A to point B. Indeed, the whole design of Linux breathes this quality and mirrors Linus’s essentially conservative and simplifying design approach.

“So, if rapid releases and leveraging the Internet medium to the hilt were not accidents but integral parts of Linus’s engineering-genius insight into the minimum-effort path, what was he maximizing? What was he cranking out of the machinery?

“Put that way, the question answers itself. Linus was keeping his hacker/users constantly stimulated and rewarded—stimulated by the prospect of having an ego-satisfying piece of the action, rewarded by the sight of constant (even daily) improvement in their work.

“Given a large enough beta-tester and co-developer base, almost every problem will be characterized quickly and the fix obvious to someone.

“Or, less formally, ‘Given enough eyeballs, all bugs are shallow. I dub this: ‘Linus’s Law’. http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/”

So, Raymond is replacing the “old heroes” with a new one, Linus. Simple and “essentially conservative.” The very words, “Cathedral” and “Bazaar,” were already in use to describe two different development styles; nevertheless, they are loaded like cluster bombs, and Raymond takes advantage of this, implying that the New Linux style is the wave of “the now” and the future, while the “old way” of the FSF—he even mentions Stallman and his most successful creation, GNU Emacs as relics of the Cathedral—is as obsolete as any old Church.

‘Cathedral vs. Bazaar’

“In Linus’s Law, I think, lies the core difference underlying the cathedral-builder and bazaar styles. In the cathedral-builder view of programming, bugs and development problems are tricky, insidious, deep phenomena. It takes months of scrutiny by a dedicated few to develop confidence that you’ve winkled them all out. Thus the long release intervals, and the inevitable disappointment when long-awaited releases are not perfect....In the bazaar view, on the other hand, you assume that bugs are generally shallow phenomena—or, at least, that they turn shallow pretty quickly when exposed to a thousand eager co-developers pounding on every single new release. Accordingly you release often in order to get more corrections, and as a beneficial side effect you have less to lose if an occasional botch gets out the door....And that’s it. That’s enough. If ‘Linus’s Law’ is false, then any system as complex as the Linux kernel, being hacked over by as many hands as that kernel was, should at some point have collapsed under the weight of unforeseen bad interactions and undiscovered ‘deep’ bugs. If it’s true, on the other hand, it is sufficient to explain Linux’s relative lack of bugginess and its continuous uptimes spanning months or even years,” wrote Raymond. http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/

I wrote to Stallman, that, according to my reading of “The Cathedral and the Bazaar,” Raymond, who used to develop GNU software, seemed to classify the GNU/FSF method of development as “Cathedral” style as opposed to the “Bazaar” style used by himself and Linus Torvalds.

Stallman’s response:

“Is he still saying this? I thought he had stopped… It is not true. There is no single GNU/FSF development method, since each package maintainer can handle this as he likes. In fact, some GNU packages tried the Bazaar model before ESR did. ... The fact is that before the Bazaar model, the Cathedral model was the only one. We used it, ESR used it, and everyone used it.... I think ESR tried to associate that model with GNU so as to make us look bad. He does not like our philosophy, so he hoped that by making us look bad, he can reduce our influence. However, I told him this was not true, and I thought he had taken it out. Hence my question about whether he is still saying this.”

Raymond went on to point out that the old corporate model of top-down design no longer applied, that developers were more apt to create great software if they were allowed to have fun while doing so, enjoy their work as opposed to living a “Dilbert” life in a cubicle; nonetheless, this applies to the corporation. Raymond’s vision of the future is one of the successful corporate software product.