Stallman — 20 Years of Explaining Free Software
H4x0r Jim Duggan writes "The first recorded talk by Richard Stallman on free software was in 1986, so I've picked from the 2006 recordings and have made a transcript of a recent talk: The Free Software Movement and the Future of Freedom. Those two are the only transcripts of his general free software talk. Others that exist are on specific topics such as patents, GPLv3, copyright, etc. For those who've been reading Slashdot during the gradual evolution of Stallman's pronouncements, it's interesting to see what has changed over 20 years."
You see when people adopted the monkier of open source software. . .
So that Microsoft could exploit the ambiguity of the word "open" to claim that their software is open source? I'm afraid the word "open" is just as open to interpretaion as any other non-technical word.
Of course RMS provided a technical defintion of what he meant by "Free Software."
The reason a lot of people prefer to use "Open Source" isn't because the term "free" is ambiguous (although I recognize the existence of the "libre" crowd); it's because they the disagree with the specificity of the term. The definition of "Open Source" is more, ummmmmmmmm, "Open."
ESR, for example.
KFG
He will never get over it.
When mswindows 95 appeared, it wasn't called "the DOS system". It was the Windows system, running on DOS. Okay, that's too much of a stretch.
mswindows nt/2000 was not the "kernel32.exe".
OSX is not "mach + some apple stuff".
An operating system is a lot more than a kernel, in the same way that a car is a lot more than its engine, even when it doesn't work without it. The user doesn't get to interact with the engine, and the car would be the same car, if the engine is replaced. That happens the same way with Operating Systems and kernels. Debian is not there yet, but they have several GNU distributions with varying kernels.
Linux is a good kernel, and plays an important role for the success of free software. Aside from that, when you get for example, Ubuntu, there is a lot more GNU than Linux included in the CD. And the platform is defined by the GNU system, not the Linux kernel.
When people say they know "Linux", for example the "Linux" console, they are talking about bash. When talking about "Linux" programming, it's usually GCC, the "Linux" desktop might be Gnome or KDE, of course, but it's not Linux either.
The guy will never get over it, because, in that particular issue, he is right, and the people who think different from him are just wrong. There's no way he will change his opinion on that issue.
GNU however could be replaced with something else. e.g. the BSD userland/libraries. Would we then be obliged to call the operating system BSD/Linux?
Not all conservatives are stupid,
but it is true that most stupid people are conservative.
- Hume
Or you could just do what most of the human population does and call it something simpler. i.e. Linux
Not all conservatives are stupid,
but it is true that most stupid people are conservative.
- Hume
A) fewer people will use the software (because it tries to prevent people from using w/o paying)
B) the software is less useful to people because they can't modify the original program
C) proprietary software is less valuable because other developers in lateral areas can't learn from it.
It seems pretty clear to me that his arguments failed on these pragmatic grounds and that he's had to shift his anti-ownership rational to far more nebulous and entirely philosophical arguments about "freedom" for its own sake.
The facts are:
A) Contrary to his "first level" of harm: proprietary software has vastly outcompeted open software despite its barriers.
B) Contrary to his "second level" of harm: that most users still prefer closed source software despite the fact that they can't tinker with it and despite the fact that it costs more/has more barriers.
C) Contrary to his "third level" of harm: that proprietary software still appeals more to its end users despite the fact that proprietary developers benefit little from the pool of open source code. This despite the fact that open source developers supposedly have a huge advantage over proprietary developers because they can exploit the GPL and other copyleft code to a level that their counterparts cannot.
In short, he's given up on his pragmatic rationale since they've been proven almost entirely wrong. I'll concede that there is something to be said for the sharing of code in some cases, but we're to choose rationally between no ownership vs choice of ownership (the status quo) that the latter is the only sensible and pragmatic choice given his own (old) arguments and the empirical evidence (or lack thereof) from his so-called copyleft movement.
I appreciate most of what RMS says. I strongly disagree with his numbering scheme for the 4 essential software freedoms. Read people count starting at 1. It's stupid to have the leader of a movement use an inside joke when giving a public talk about something so important. Freedom zero.... How stupid.
Hey Richard, how many freedoms are there?
Four.
What's the fourth one?
There isn't one... Only a zeroth through third.
This nonsense has got to stop. The GPL is fairly readable, but this stupid geekism right there mixed in with the fundamental freedoms is IMHO just adding confusion where none needs to be. I would hope this renumbering will make it into GPLv3.
See the thought experiment. Take Photoshop: if you offered a user the choice to take Photoshop with no access to the source vs. complete access to the source, what do you think that most people would choose, all other things (including price) being equal?
The third level of harm doesn't have much to do with the end users, anyway. However, to continue the thought experiment: in an office environment, would you rather have open-source printer drivers you could get tech support to fix on-site (or vendor patches if already fixed), or closed-source printer drivers that require vendor support?
I think that your arguments focus on the wrong side of the point. Proprietary software is popular, true. That doesn't mean that open sourcing it would make it less popular.
I [may] disapprove of what you say, but I will defend to the death your right to say it.
- Anyone may read this specification and implement it.
- Anyone may read this specification, but there are conditions on implementations.
- Anyone who gives us a load of money can implement this specification.
The same is true of 'open source.' There is a legal definition on the OSI site, which is very long, and far less concise that the FSF's four freedoms, but without it the term is highly ambiguous. Is Microsoft's Shared Source initiative 'open source?' You and I might know that it isn't, but anyone can download the source and read it, so it certainly sounds open.I am TheRaven on Soylent News