EOF - A Tale of Two Futures
We've long since lost count of free and open-source (FOSS) codebases. Last I heard, the sum was passing half a million. If we were to visualize these as a tree, it would resemble a banyan—wide and flat, a forest in itself, with one main trunk in the middle and smaller ones under its radiating branches. That main trunk would be Linux. The ground would be the Internet.
Why has this vast organism grown so broadly and rapidly, with no end in sight? Many answers may come to mind, but I suggest one that should be new to Linux Journal readers—as it was to me, when I first heard it from Jonathan Zittrain. That answer is generativity.
In his new book, The Future of the Internet—And How to Stop It (Yale University Press, 2008), Jonathan defines generativity as “a system's capacity to produce unanticipated change through unfiltered contributions from broad and varied audiences”. In an earlier research paper, “The Generative Internet”, he explained, “The grid of PCs connected by the Internet has developed in such a way that it is consummately generative. From the beginning, the PC has been designed to run almost any program created by the manufacturer, the user, or a remote third party and to make the creation of such programs a relatively easy task.”
Linux and the FOSS portfolio fit this description, and so do its developers. In fact, I submit that both are even more generative than the wide-open machines they put to work. But, although it would be nice to see FOSS programmers credited with setting new records for generativity, what I'd rather see is those same programmers playing a leading role in preserving and expanding the Net's generative power.
According to Jonathan, the future does not default to rosy. In fact, he says the Net's generative growth is stalling. “The future unfolding right now is very different from its past”, he writes. “The future is not one of generative PCs attached to a generative Internet. It is instead one of sterile appliances tethered to a network of control.” Among those appliances, he lists Microsoft's Xbox 360, Apple's iPhone and TiVo DVRs. Thus, we stand at a fork between two futures: one generative, the other applianced—and the fight being won by the latter.
Linux and FOSS programmers are not innocent bystanders in this fight between futures. They contribute to both. As Jonathan puts it:
...generative and non-generative models are not mutually exclusive. They can compete and intertwine within a single system. For example, a free operating system such as GNU/Linux can be locked within an information appliance like the TiVo, and classical, profit-maximizing firms like Red Hat and IBM can find it worthwhile to contribute to generative technologies like GNU/Linux.
The generative/applianced divide is one between cultures as well as work, and we have geeks laboring on both sides of it. One side creates code that is both useful and re-usable—whether it's a leaf on the collective FOSS banyan tree, or humus in the networked ground on which that tree grows. The other side does what The Man tells it to do, even if the job is equipping an appliance to do something closed on top of open code.
What's strange is that both are mundane. They are not romantic. They do not supply fodder for partisan arguments. They are not box office. They are simply useful. This enormously productive (and reproductive) practicality is perhaps the most plain yet overlooked fact about FOSS development. Even within our community, we don't think much about how successful, common and purely generative our work is—and how much it has contributed to the growth and success of the Net. We just do good work, have fun and press on.
Yet there are these two sides. One thrives in the open world while the other disappears into machines. One makes stuff that is NEA: Nobody owns it, Everybody can use it, and Anybody can improve it. The other makes stuff that is OOO: One company owns it, Only its customers can use it, and Only the company and its captive partners can improve it.
Perhaps both will win, but maturing markets preponderate toward the simple and the predictable, rather than the complicated and the chaotic. For technology, that favors the applianced over the generative.
I've always been an optimist about generativity, even though I didn't know the word until a few months ago. But I see Jonathan's case, and it has me worried. There is no shortage of closed appliances that run Linux. Sometimes we don't even know they're around. Both my Sony Bravia 1080p flat-screen and the Dish Network set-top box that feeds it have Linux operating systems. And, both are built to prevent far more generativity than they enable.
Back in 2002, I wrote a piece titled “A Tale of Three Cultures” (www.linuxjournal.com/article/5912). One culture was FOSS hackers. One was embedded systems programmers. And the third was Hollywood, feeding popular culture. Toward the end of that piece, I offered a challenge: “And if we are asked by our employers and our government to replace the people's Net with a corporate digital rights management system, will we go about it as heads-down technologists? Or will we refuse to build it?”
That challenge still stands.
Doc Searls is Senior Editor of Linux Journal. He is also a Visiting Scholar at the University of California at Santa Barbara and a Fellow with the Berkman Center for Internet and Society at Harvard University.
Doc Searls is Senior Editor of Linux Journal
|Non-Linux FOSS: libnotify, OS X Style||Jun 18, 2013|
|Containers—Not Virtual Machines—Are the Future Cloud||Jun 17, 2013|
|Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer||Jun 12, 2013|
|Weechat, Irssi's Little Brother||Jun 11, 2013|
|One Tail Just Isn't Enough||Jun 07, 2013|
|Introduction to MapReduce with Hadoop on Linux||Jun 05, 2013|
- Containers—Not Virtual Machines—Are the Future Cloud
- Non-Linux FOSS: libnotify, OS X Style
- Lock-Free Multi-Producer Multi-Consumer Queue on Ring Buffer
- Linux Systems Administrator
- Validate an E-Mail Address with PHP, the Right Way
- Introduction to MapReduce with Hadoop on Linux
- RSS Feeds
- Weechat, Irssi's Little Brother
- New Products
- Tech Tip: Really Simple HTTP Server with Python
- Poul-Henning Kamp: welcome to
2 hours 1 min ago
- This has already been done
2 hours 2 min ago
- Reply to comment | Linux Journal
2 hours 48 min ago
- Welcome to 1998
3 hours 36 min ago
- notifier shortcomings
4 hours 12 sec ago
5 hours 37 min ago
- Android User
5 hours 38 min ago
- Reply to comment | Linux Journal
7 hours 31 min ago
10 hours 21 min ago
- This is a good post. This
15 hours 34 min ago
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?