Being Free is Hard to Do
ValourX writes "What is more important to you -- the four freedoms of Free Software, or the ability to maximize the value of your computer? It's a question that comes up on Slashdot often, but rarely is it so well argued as it is in this NewsForge article. How important are the FSF's four freedoms to you? What are you willing to sacrifice for those freedoms?" NewsForge and Slashdot are both part of OSTG.
What is more important to you -- the four freedoms of Free Software, or the ability to maximize the value of your computer?
I suppose that depends on how you define "value". Personally, having Free Software and using Free Software has done more to "maximize the value" of my computer far more than anything else I can think of.
SealBeater
-- Its survival of the fittest...and we got the fucking guns!!!
Look up the following: Mplayer, Kaffeine, Xine, LibDVDRead and BZFlag. Not replacements for closed source, really. Far better, IMO. As for ruddy games, that's what the Cube, PS2, Xbox et al are for (yes, in direct contradiction of me mentioning BZFlag. I can be ignorant, too).
You may also want to look at Mozilla, Firefox, Kmail (which, IMO, is the best graphical mail client ever coded), The GIMP, the FreeBSD networking stack and ipfw. These are all bits of open source software that I use on a daily basis that are "in-my-face" and noticeable. They are also the reason I would be lost without my open source OS, along with the myriad other packages running out of sight and mind that keep my computing and networking ticking over without a hitch. Being free hasn't cost me anything, so I guess I'm not qualified to comment...
Resistance is futile. Reactance buggers it up.
Having done both, I'd disagree with that "always".
Where I currently work, we have strong, well-understood and well-followed processes that result in higher-quality code - source control, design and code reviews, requirements gathering, etc.
Too often in a project "done for love" these things get ignored (yes - that happens very often when done for money too). That's because (a) setting these things takes time away from the fun part of the project and (b) often the person doing the project for love just doesn't understand the need for it or (as in my case) isn't disciplined enough to do it without a framework in place (both process and social).
There are examples and counter-examples all over the place - I'm just saying don't be blind to the idea that work done for pay can be superior.
People tend to forget what launched Mr. Stallman on this road toward software freedom: he wanted to use a laser printer he had on hand with his word processing program. The software didn't have drivers, and as I recall the printer didn't have documentation, either.
Big trees from little acorns grow.
I suppose I'm spoilt by FBSD's ports system where stuff generally works out of the "box" immediately. I hear Debian's apt-get does similar, looking after dependencies automatically, although I would be a bit disappointed with Debian's time-to-update.
;-)
You're right, of course. Folks don't want to spend an hour compiling things, and this is where Big Bill and the TC mob have the upper hand. They just want to slam the DVD in the hole and get the latest drivel on the screen and to hell with privacy and control. Me? I like knowing I'm in control. With FOSS, I am. With XP and Media Player who knows who is pushing the damn buttons? Have you ever run a tcpdump on a router supplying a virgin XP SP2 machine with connectivity? It's all subjective.
In a way, FOSS has forced me to learn a bit more about what I'm using. It now takes me ten minutes to install a fully functional Kaffeine using libxine on a FBSD box. When I first tried with gmplayer on Slackware, it took me two days full-on geeky head-in-the-Makefile messing and that's without getting X working in the first place. My family now happily do all the things they once did on Windows on a FreeBSD desktop system, replicated from my own desktop after each upgrade, which is far easier than keeping XP updated. The subjective here is have I lost or gained? Me? I reckon I've gained. Of course, the AMD64 helps with the wall time figure I just quoted
Resistance is futile. Reactance buggers it up.
Freedom is the ability to do something without the fear of punishment.
For example, my ability to practise Judiasm in the US without fear of persecution typifies "freedom of religion" in the idealistic sense. But a more devout Jew is not necessilary free in a total sense. Employers might not allow days off for Jewish Holidays, or even more important Friday night/Saturdays for the sabbath. Someone may be ridiculed by a co-worker for wearing a kippah. Of course a more devout Jew (which I'm not) could work for a different employer, and only deal with people who accept the way he dresses. (Doesn't this sound familiar... RMS would say you shouldn't work for an employer who makes your write proprietary software.)
The point here is freedom is not something that one person has, but rather is a state of mind between two or more people. If you are accidentially stuck alone on an island, freedom has no meaning. You may not have the *ability* to leave the island, but freedom itself has no context since you are not dealing with other people.
Now taking the island concept further: if you live on an isolated (from the rest of the world) island with friends and family, you could copy / modify / distribute software all you want if its mutually agreed that that's okay. Many people have considered their personal and other friend's/family's computers to be such an island. With the internet though, you are in full contact at all times with people / government / etc. who are set on punishing for such acts.
So keep in mind, you can fight for freedom all you want from a legalistic / systematic / technical / software-based way, but ultimately, freedom is a mutal agreement between people. Whenever someone is out there who is willing to punish you in some extent for what you are doing, you have a noticable reduction in your freedom. Of course, if value your freedom, you then must fight for it.
The obsession to endow software with the concept of freedom is thus misleading. People have freedom, software does not. So GPL-licensed software is *freedom-enabling* software (to a certain extent). Its using copyright law to prevent other people from punishing you.
So as we look towards a revised GPL 3.0, we should really keep in mind separate ideas of "freedom" and "ability". We need the ability to have source code availible in order to modify/understand software many years down the line (even after threat of copyright expires). Just as we need the freedom to create software without the threat of punishment by frivolous software patents.
When looking at the GPL, thus imagine it in two ways:
1) If I isolated, what abilities does the GPL ensure I still have? (access to source code, ability to modify, ability to copy, etc.)
2) As I deal with other people, what punishments am I trying to prevent? (copyright hoops to jump thru, ridiculous licensing restrictions, patent lawsuits)