Guest Editorial: World Domination

World domination. It's a powerful and faintly sinister phrase, one you might imagine some B-movie mad scientist muttering as he puts the finishing touches on some infernal machine amidst a clutter of bubbling retorts and crackling Tesla coils. It is not a phrase you would, offhand, associate with cuddly penguins.
When Linus says he aims at world domination, it seems as if he wants you to laugh at the absurd image of a gaggle of scruffy hackers overrunning the computing world like some invading barbarian horde—but he's also inviting you to join the horde. Beneath the deadpan self-mockery is dead seriousness—and beneath the dead seriousness, more deadpan self-mockery. And on and on, in a spiraling regress so many layers deep that even Linus probably doesn't know where it ends, if it ends at all.
The way Linux hackers use the phrase “world domination” is what science-fiction fans call a “ha-ha-only-serious”. Some visions are so audacious, they can be expressed only as ironic jokes, lest the speaker be accused of pomposity or megalomania. It is in much the same spirit that I sometimes describe myself as Linus' Minister of Propaganda, as if I were some evil communist bureaucrat in a campy remake of Orwell's 1984.
Such conscious self-subversion can serve many purposes. There's a touch of Zen in it—a reminder from ourselves to ourselves not to take our desires so seriously that we stop noticing reality. It's also tactically valuable. Like the cuddly penguin mascot, it invites our most dangerous adversaries not to take us seriously. They're serious-minded people themselves, too caught up in competitive testosterone games to have any room for Zen. When they hear “world domination”, they don't hear the irony, and thus tend to write us off as nutcases or flakes. That's good; it gives us time and room to blindside them.
Of course, articles like this are part of that game. We hackers are a playful bunch; we'll hack anything, including language, if it looks like fun (thus our tropism for puns). Deep down, we like confusing people who are stuffier and less mentally agile than we are, especially when they're bosses. There's a little bit of the mad scientist in all hackers, ready to discombobulate the world and flip authority the finger—especially if we can do it with snazzy special effects.
So, “World domination now!” we declaim, grinning at the hapless suits and wondering which ones are smart enough to be in on the joke. Because, of course, a world of mostly Linux machines wouldn't really be a domination at all. Linux has no stockades, no guard towers, no barbed wire, and no End User License Agreement saying you can't modify and can't look inside and don't have any kind of title to the bits on your own disks. When Linux “dominates”, there won't be any predatory monopolies bluffing, bribing and bullying competitors to protect the market for their own overpriced and shoddy software. When Linux “dominates”, software consumers and developers will win big—and only the kind of people for whom domination really does mean controlling other peoples' choices will lose.
That's a future worth working for. Linux world domination means no domination anywhere—a statement which is ironic in the strict rhetorical sense (“expression of something which is contrary to the intended meaning”) but dead serious all the same, and no regress need apply.
No domination anywhere, but rather a rich ecology of competing projects and distributions and customizations, each one of which constantly brings its own improvements to the globally shared code base. A world not of closed pseudo-standards that lock people in, but rather of true open standards that enable humans and programs to cooperate in ever-richer ways. A world not of lock-step uniformity and five-year road maps, but rather one of rapid evolution and variation and flexibility and almost instant market responsiveness to user needs. A world in which programming means solving new problems every day, instead of wastefully repeating work that somebody else locked up and hid away. A world in which play becomes the highest form of work, and vice versa.
The future of “no domination anywhere” will be a better world; not a perfect one, but perhaps the best that we, working as designers and programmers, can hope to create. So if you aren't yet part of our barbarian horde, join us! There's a lot of working and playing to be done in order to get from here to there. It won't be hard to find us; we'll be the mob yelling “World domination now!”--and smiling.
Eric Raymond is a Linux advocate and the author of The Cathedral & The Bazaar. He can be reached via e-mail at esr@thyrsus.com.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Designing Electronics with Linux | May 22, 2013 |
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
- RSS Feeds
- Dynamic DNS—an Object Lesson in Problem Solving
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Validate an E-Mail Address with PHP, the Right Way
- What's the tweeting protocol?
- Tech Tip: Really Simple HTTP Server with Python
- Kernel Problem
1 hour 42 min ago - BASH script to log IPs on public web server
6 hours 9 min ago - DynDNS
9 hours 45 min ago - Reply to comment | Linux Journal
10 hours 17 min ago - All the articles you talked
12 hours 41 min ago - All the articles you talked
12 hours 44 min ago - All the articles you talked
12 hours 45 min ago - myip
17 hours 10 min ago - Keeping track of IP address
19 hours 1 min ago - Roll your own dynamic dns
1 day 14 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?




Comments
World Domination
Nice thought :)