|
|
|
|
|
by swhipple
3474 days ago
|
|
To add on to your point, this is called the 'paradox of freedom' -- that you cannot have both unlimited freedom and ensure freedom for the future. At the end of WWII, Karl Popper defended state interventionism with an argument citing the paradox of tolerance [1], and claimed ensuring a tolerant society in the name of tolerance, even when paradoxically intolerant. A parallel argument can be made in Stallman's case for copyleft to be claimed in the name of freedom. It's also worth noting that it is not only Stallman's FSF that uses this definition w.r.t intellectual property nowadays. Lessig's CC adopted the same terminology for their share-alike license (-SA), which has the goal of preserving freedom, while -NC or -ND are considered non-free because they contain restrictions not related to this purpose. The same is true in the greater free-culture community and academic contexts from my experience. [1] http://www.goodreads.com/quotes/25998 |
|
In practice the "freedom" is exclusive to a highly educated and exclusive technocracy. The same freedoms are not available to the general public.
This may seem pedantic, but IMO it undermines the argument about software freedom, because Stallman has never shown the slightest interest in making software that the general public can modify, or in designing, promoting, or doing anything at all to encourage the existence of such software.
The idea that if you want to promote software freedom you need to make tools and systems that ordinary people can modify - preferably without learning Emacs - doesn't seem to have occurred to him. It seems that in Stallman's world the public are supposed to become MIT-grade hackers before they can earn their freedom.
You could argue that software is hard, and that's just how it is. But I'm not so sure that's true. It's not obvious that the hardness of software isn't a side effect of the culture around it, and not something unavoidable in the process of development.
The reality is that there has been almost no serious CS research into making accessible user-modifiable systems. FSF would be more convincing if there had been at least some token effort in that direction. But instead FSF has always promoted a rather old-fashioned and nostalgic view of computing, where everything happens on the command line, and development means hand-editing source code and running a build system to create a local binary.
That was more or less the only model around in the 1960s and 70s, but things have moved on since then. Unfortunately the FSF mostly hasn't.
Given that, the question is - what does software freedom mean to users now? If source code doesn't actually equal freedom - what does?