EOF - The Power of Definitions
As a concept, freedom is usually defined two ways, one negative and one positive. Freedom from is the negative. Freedom to is the positive. Countless social and political causes grow around the need for freedom from—slavery, oppression, poverty, taxation—anything that limits our freedom to act, move, associate, choose.
The freedoms described by the Free Software Definition (www.gnu.org/philosophy/free-sw.html) are all positive:
The freedom to run the program, for any purpose (freedom 0).
The freedom to study how the program works, and adapt it to your needs (freedom 1). Access to the source code is a precondition for this.
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to improve the program, and release your improvements to the public, so that the whole community benefits (freedom 3). Access to the source code is a precondition for this.
These freedoms are also personal: “Free software is a matter of the users' freedom to run, copy, distribute, study, change and improve the software”; and “a program is free software if users have all of these freedoms.”
Freedom is a profoundly human value. We are, more than any other species, devoted to originality, and we savor values that express it: intelligence, talent, choice, craft. Other animals make things too. Birds build nests, ants build hills, beavers build dams, bees build hives. But it is the nature of each to build these things the same ways as others within the species. Every human is different. What we value most in people is what makes them different from other people and what they do that's different. Freedom maximizes the scope of those differences and of our originality.
Software is one among countless other original human creations, but with an essential difference: it has no physical substance. Even the ephemeral creations we call music and speech are waves compressed within air. Software is something else. It is code. At a deeper level, it is binary math: ones and zeros.
Humans make sense of things through their bodies. Good is “up” and “light”, while bad is “down” and “dark”, because we are upright-walking diurnal animals. If we had the bodies of raccoons, we might say the opposite. Our worlds are full of metaphorical understandings grounded in our physical structures. When we say, “He picked my face out of a crowd”, we use the metaphor seeing is touching. When we say we “grasp a concept”, we use the metaphor understanding is grasping. What we do with our bodies shapes what we know in our minds and how we talk about it.
Yet software isn't physical. We need help understanding it, or we'll mess up by understanding it with misleading metaphors (for example, that it's a packaged good, like cereal). This is why we need to start with deep insights into software's nature, and into connections between that nature and our own. The Free Software Definition provides those. So does the companion concept of copyleft (www.gnu.org/copyleft/copyleft.html), which protects the liberties inherent in free software. This is why Richard M. Stallman calls free software a “social movement”, while positioning open source as a “development methodology” (www.gnu.org/philosophy/open-source-misses-the-point.html).
Today we live in a networked world not only filled with free software and open-source code, but also increasingly organized and defined by it. This has caused problems of perception that are similar to those that required the Free Software Definition 25 years ago.
The Internet, for example, has become a form of infrastructure, yet it lacks the physical qualities that have defined familiar forms of infrastructure in the past. Although it embodies qualities that are similar to real estate (“sites” and “domains” with “addresses”) and transport systems (“pipes” and “highways”), its supportive capacities are categorically limitless. This is why restricting our understanding of the Net to real estate and transport metaphors is a mistake.
Ask ten people to tell you what the Net is, and you'll get ten different answers. The same won't happen if you ask them what a road or a water system is. Or a phone or cable TV system. An irony in that last case is that telephony and television are now forms of data. In February 2009, here in the US, analog broadcast television will go the way of the steam locomotive. All TV broadcasting will be digital. Yet it will still be represented in familiar analog-like ways, with “channels” from “networks” and so on. Lost is the fact that these things are coming to homes by digital signaling using Internet protocols.
Where I live in California, burying service underground is a huge chore. The ground is rocky, and underground service culverts need to be eight feet deep, so there's room to keep electrical, cable TV and telephone services separate, just like they are on the poles above the ground. Yet the old analog phone wiring and coaxial TV cabling are no longer required. Being just data, telephony and television can be carried on fiber-optic cabling. And that cabling can run right next to high-voltage electrical wiring, as fiber-optic signaling is unaffected by proximity to electric current. The smart thing to do, then, is to trench the dimensions required for electric service, and run the rest over fiber-optic cabling alongside it.
But we're not ready for that, mostly because we still see the Net as a grace of telephone or cable company carriage—not as something that's essentially free and open. Yes, capital outlays are required, but the upsides of making those outlays are incalculably large, for everybody.
So our problem with the Net is very similar to the problem we had with software up to a quarter century ago: it's seen as essentially proprietary. We think of it as something owned and/or controlled by a big company and delivered as a “service” that we “access”. Although that's how most of us “get” the Net today, that understanding is at odds with the Net's free and open nature, and with our own as sources of value for the Net.
What we need now is a definition of the Net that is as deep and useful as the Free Software Definition's is for software. Without that definition, the Net will continue to be defined mostly by government, and by phone and cable companies.
Doc Searls is Senior Editor of Linux Journal and a fellow with both Berkman Center for Internet and Society at Harvard University and the Center for Information Technology and Society at the University of California, Santa Barbara.
Doc Searls is Senior Editor of Linux Journal
|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|
|Non-Linux FOSS: Seashore||May 10, 2013|
- 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
- Validate an E-Mail Address with PHP, the Right Way
- A Topic for Discussion - Open Source Feature-Richness?
- Drupal Is a Framework: Why Everyone Needs to Understand This
- RSS Feeds
- Readers' Choice Awards
- The Secret Password Is...
- All the articles you talked
43 min 30 sec ago
- All the articles you talked
46 min 37 sec ago
- All the articles you talked
47 min 57 sec ago
5 hours 12 min ago
- Keeping track of IP address
7 hours 3 min ago
- Roll your own dynamic dns
12 hours 17 min ago
- Please correct the URL for Salt Stack's web site
15 hours 28 min ago
- Android is Linux -- why no better inter-operation
17 hours 43 min ago
- Connecting Android device to desktop Linux via USB
18 hours 12 min ago
- Find new cell phone and tablet pc
19 hours 10 min ago
Enter to Win an Adafruit 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
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?