I learned this trick when I was a strict vegetarian. I wasn't eager to confront people about their meat-eating, but when you don't eat meat, people pretty quickly jump to the conclusion that you think they're morally wrong to eat meat. The tension bothers them, so they bring it up in some awkward way. When my girlfriend's father did that (and later at one point her boss, at a company barbecue) I didn't want to get into the details, so I just said, "Well, it's a complicated issue." It was an honest statement, and I really had no idea exactly where I stood on eating meat, but I was so impressed with how completely it put them at ease and averted all conflict that I stored that memory away. Since then, I have used it many times dishonestly to avoid conflict with people who had power over me, my friends, or my family. Seeing gray is a "get out of conflict free" card.
I think the only time it takes bravery to see gray areas is when everybody else sees black and white. Otherwise, the "ability" to see gray helps you paper over disagreements and maintain valuable relationships with people.
Also, it usually isn't correct to think that a person avoids addressing gray areas by being black-and-white on a certain question. I am single, and for me, sex is an endless gray area. I have a conservative Christian friend who doesn't see any gray at all when it comes to premarital sex, but not because he's stupid or unthoughtful. He has to deal with gray areas in other places, such as divorce and state-mandated immunization against HPV. (His daughter will be immunized, and he thinks that's okay. He has friends who think it's not, and who are shocked by the fact that he doesn't resist in some way.) RMS sees gray areas in the use of non-free technology, and he makes concessions to reality. He's proud of his ability to use a completely free computer system, and he understands that it isn't practical for everybody, and he knows that even his success is limited to a very small portion of the technology that contributes to his existence. That's a gray area! I can understand where he's at. When I was a vegetarian, and now as a near-vegetarian, I know some people might think I'm being black and white to subsist on beans and potato salad at a catered barbecue lunch, but I think I'm being plenty "gray" by eating beans from a barbecue joint without asking why they taste so darned good. Everyone's thinking is gray someplace; the perception of "black-and-white thinking" is created by an observer focusing in on a certain place where he expects to find gray and is surprised to find black or white instead.
Sounds legit.
> RMS would [refuse a Nobel] without any questions.
What's the difference between a Nobel and a MacArthur Genius grant?I would gladly accept either honor :-)
A Nobel prize, by contrast, is only given in certain fields, which already constrains the way that it is perceived. With a MacArthur, you're not necessarily competing against others in your field, because you oftentimes don't have a field (what you do is so highly specialized that nobody else really comes close). Furthermore, the prize is a political tool as much as anything else nowadays. (Looking at many of the recent Nobel Peace Prize recipients, I think anybody would agree to that.) The MacArthur has much less political identification, even compared to the prizes for biology/chemistry. It's nice to be able to attach it to your name when convenient as it gets a little bit more respect, but it's hard to interpret it in a negative way (or to see a recipient of a MacArthur as somehow compromising his/her views -- remember that Stallman has rather weak opinions on money per se when it comes to freedom; one can have a FLOSS product that nevertheless generates money).
(And as for the awards, I agree - at this point in my life I would probably be satisfied with either one!)
AKA Fanaticism. He's become an inflexible, computerized hermit. His dogmatic adherence to a demonstrably untenable principal of "freedom" has relegated him a permanent state of pre-1995 digital stasis.
He's not principled, he's dogmatic. At best, he's a cautionary tale demonstrating the state of the world if he had his way.
How do you know what the state of the world would have been if he had his way? All you know is his state in our current world, which is vastly different from a world with nothing but free software. You think hardware manufacturers wouldn't use free software if that was all that existed?
You have no idea what the world of technology would look like if we had nothing but free software. And neither do I, and neither does Richard Stallman. But we do suspect it would be better. At the very least, don't discount the possibility.
Almost all of the things you consider modern in the computer world are built on top of his creations. OS X, google, facebook, HN, etc ... all built on the foundation RMS laid. Without his creations we would be closer to your idea of a "pre-1995 digital stasis"
Of course it's a difficult exercise to try to imagine how things would be different had the FSF not been created, or what influence it had upon the creation of software that wasn't directly affiliated with it. Obviously gcc has been one of the most prominent GNU toolsets featured in modern operating systems, although that appears to be changing too (Xcode replacing gcc with LLVM).
OS X used all the major GNU tools, and was built with GCC. Without his creation you wouldn't have been able to build OS X.
The foundations of Google and Facebook are ultimately the GNU toolset. Everything you mentioned, php, apache, python, are built on top of the GNU tools.
GCC and the build chain is about all I can think of off the top of my head. Most of the userland is from FreeBSD.
And GCC and the build chain are quickly being replaced.
He's a living, breathing demonstration of the limits of free software. A world where progress slows to a crawl because the only people who have the time to write code are hobbyists and people who can get paid to lecture about how everything should be free.
That's the main issue I have with his ideas, they are thoroughly disconnected from reality. Not in a "Everyone should be nice to each other all the time way," but a "I'm going to ride my dragon to work," way.
Free software is a nice sentiment, but impotent. Nothing that has happened in the past 10-15 years in computers happens without a profit motive. Without a profit motive you may get a spreadsheet program, but no one motivated enough to get it distributed.
Free may get you on the path, but it doesn't get you very far down the road.
Software is either free or it's not free. It's either restricted or it's unrestricted. It's either proprietary or it's open.
Using hyper-capitalistic entities like Google and Facebook as a defense of the viability of free software is an interesting way to go. If anything, I'd argue they are almost perfect subversions of Free Software. Going a little deeper, a place like Y-Combinator is an even further subversion because, at it's core, it is a company that specifically exploits the profit motive of developers.
That aside, I think it's not particularly useful to argue that Stallman's contributions to the field are a vindication of his basic philosophy. Especially when those contributions are being used in a way that subverts it.
I've visited the building where Red Hat has their Brazilian office (or, at least one of them). Nice place for a non-profit.
The argument it's not possible to make money and, at the same time, respect the rights and freedoms of users is an old one. We shouldn't be hearing it anymore.
Please, demonstrate away.
The more I live, the more I realize that old men without or with messed up sex lives are not to be trusted as gurus or guides in life.
It's the Pied Piper of Hamelin all over again.
It is my philosophy that one should go through all stages in life in order, otherwise one will never be happy, though timing is not as important as order. I've seen old people get bitter and resentful when they see youth partying and going out -- because they themselves had never done so when they were young.
One of my favorite quotes from Nietzsche (though this guy also had a messed-up/nonexistent sex life): "Man is something to be surpassed, but only a buffoon thinks that man can be overleapt." Surpass but don't skip.
ie; what car does he use and own? All (modern) cars accept software updates which is his definition of a computer. Most modern televisions, dvd players, routers and even some microwaves/refrigerators can take firmware updates also.
Genuinely curious about the above - Not being a troll, just wondering how far the man really takes his beliefs. Does he stop at the most publicly noticeable devices ( laptop/cellphone ) or does he go all the way.
Yes, as far as I know.
ie; what car does he use and own? All (modern) cars accept software updates which is his definition of a computer.
I am pretty sure he doesn't drive, but this is what he had to say on the topic:
So, what about cars? Free cars would mean you are free to modify them and redistribute copies. Well, as for the modification, you are free to do that-lots of people modify and customize their cars. But when it comes to redistributing copies, the fact is we don’t have the technology to do it. There is no automatic car copier. Cars, today, are like books before the Xerox machine-the only feasible way to make copies was with a special factory. Copying your car is so hard that it makes little practical difference whether you are allowed to do this. Perhaps someday, through nanotechnology perhaps, a car copier will be developed. Then a Free Car Movement will be necessary.
Buggy software can cause the Lithium batteries under your seat to overheat and, maybe, catch fire. Perhaps violently.
'Category error' does not mean a quantitative or scale difference at all.
It can be examined and changed, but it's not as easy as recompiling its engine.
The reason that he promotes free software is because software is capable of being free, that is, it is logistically realistic that people freely copy, modify, and distribute it. From this, he extrapolates that there is a right to copy, modify, and distribute software. If would be physically capable of modifying the code, but is legally prevented, then that is a restriction on his rights.
Under his reasoning, it also does not apply to firmware. Because it is so tied to the underlying hardware, it's not really possible to copy or modify it in any useful way. It is certainly free, in the monetary sense, but there are no useful results of doing so. Therefore, closed software does not restrict your rights in a meaningful or non-trivial sense.
Note that this is just my interpretation of what I've read of him, and I don't follow the Free Software thing that closely so I could be mis-interpreting key points.
Firmware has changed over the years, as have the devices we embed it into. Thee devices are much more complex and capable, sometimes, smarter than the computers they connect to. I have worked with devices that ran MS-DOS-like OSs and applications on 386-class processors with built-in printers running a real-time Unix-like OS on a 32-bit RISC processor.
Also, many different devices share common hardware and designs. Hundreds of routers and other various networking devices currently run OpenWRT firmware instead of their original software. Those little boxes are smarter than the first Unix machines I used and at least an order of magnitude smarter than the Burroughs B-500 mainframe that ran land taxes for a whole city on my first internship. All it lacks is a line printer and tape drives.
Do you have perfect moral consistency in everything you do? I don't. I'd guess that it's not even possible, let alone human nature.
Why should you be allowed to take away the Freedoms of others? The one thing the GPL restricts is your Freedom to restrict the Freedom of others. That's the foundation of copyleft: your rights stop where mine begin, and that includes being granted the four Freedoms of software as defined by the FSF.
In an ideal world, we would not need the GPL. Everyone would have realized already that it is in no one's prolonged interest to make proprietary software, and it would be frowned upon to do so. We would have implicit CC-BY (or -Zero) for everything and be done with it. No more copyright and licensing crap.
No one's freedom is being taken away when you create a proprietary fork. They are not forced to use your software, and the original is still intact. You do not automatically have a right to someone else's creation.
I don't mind paying for software, and I don't mind if they don't let me see their code the same way I don't mind when my local restaurant doesn't let me inspect their kitchen just because I want to.
You're free to make forks for your own personal usage and never give anyone the source. You don't even have to tell anyone that you did.
As soon as you share that software with anyone and refuse to hand over the source, and deny the recipient the right to modify and/or redistribute your program, you are taking away that person's Freedom.
>You do not automatically have a right to someone else's creation.
Then why do you insist on taking someone else's creation and basically make it your own by taking away the Freedoms granted to you by the original creator?
If find it highly unethical to want access to Free Software without having to actually contribute to it. It's demanding rights without wanting to have to deal with the responsibilities that come with those rights. It's selfish and greedy.
>I don't mind paying for software
Except money's got nothing to do with Free Software. It's explicitly stated that you're allowed to charge for distributing copies. I'm sick and tired of this "argument". It pops up every time Free Software is discussed here and elsewhere, and the only thing it proves is that the person bringing it up has not understood what Free Software is about in the first place.
I'm not taking away anyone's freedom, unless "freedom" has some definition I'm not aware of. You might be confusing "freedom" with "right", but I'm not taking away any right either unless I specifically violate the license. You do not automatically have the right to someone's work.
> Then why do you insist on taking someone else's creation and basically make it your own by taking away the Freedoms granted to you by the original creator?
It's not a freedom if the original creator forces me to release my code. Do you see how someone forcing me to do something isn't a freedom?
> If find it highly unethical to want access to Free Software without having to actually contribute to it. It's demanding rights without wanting to have to deal with the responsibilities that come with those rights. It's selfish and greedy.
No where did I say a proprietary fork wouldn't contribute back. Merely it shouldn't be forced to open up its codebase. You can make a proprietary fork of a project and still contribute back. I would like the freedom to choose which parts I contribute.
> Except money's got nothing to do with Free Software. It's explicitly stated that you're allowed to charge for distributing copies. I'm sick and tired of this "argument". It pops up every time Free Software is discussed here and elsewhere, and the only thing it proves is that the person bringing it up has not understood what Free Software is about in the first place.
You've missed the other part of that paragraph— the part having to do with Free Software.
However, if I give you a binary of the code, but do not give you source, I have taken your freedom away?
For that to make sense, there must be something you could do before I gave you the binary that you can no longer do. Please name what that thing is.
In short your freedom is an egoistic tactic where you take, use and even abuse but dont care. There are people like RMS who think otherwise; they want a world where everyone shares to everyone so that everyone benefits from all derivatives.
In your quest for "freedom", you're endorsing a license that forces people to do something. Isn't that the very antithesis of freedom?
that "something" is crucial to the argument; GPL forces people to open their sources to ensure the freedom to use/distribute is passed further down the chain and to the future. Think of a BSD-licensed device driver; if a company forks it and makes it proprietary, develops a different but new device and sells the device with the new driver; Neither the users nor I; the original developer will be able to benefit from the derivative work and will end up with an unusable new printer in case the company ends support or does not solve a specific problem. I, as the developer and many users will end up in need to re-invent the wheel and improve the old copyleft driver.
So I the original developer, in case I give away my code with BSD license, end up allowing a permission to someone who does not give the same to everyone (and to me).
That seems like her freedom to you, but it is the freedom for one to end the freedom for many and to the original developer, in the long term, especially considering we all live in the same ecosystem finally. If BSD was ethically/not forceably used by every fork-er, that would be ultimately the same idea with copyleft.
Everytime I am giving away some code, I face this dilemma (I have MIT/BSD contributions too). I don't want to strengthen abusers, and non-contributors.
> Think of a BSD-licensed device driver; if a company forks it and makes it proprietary, develops a different but new device and sells the device with the new driver; Neither the users nor I; the original developer will be able to benefit from the derivative work and will end up with an unusable new printer in case the company ends support or does not solve a specific problem.
How likely is that, though? If you release your code under GPL, they'll just write their own version and keep it proprietary. At least with BSD, you'll have the same base if you needed to rewrite their driver.
A BSD license benefits the market and end user, while a GPL license benefits other developers if they decide to use your code to begin with.
> Everytime I am giving away some code, I face this dilemma (I have MIT/BSD contributions too). I don't want to strengthen abusers, and non-contributors.
I feel the same way, but I'd rather have code people can use without worrying about the license versus forcing other developers to adhere to my personal belief system. Your reason for using GPL sounds like the reason some publishers use DRM: They do not want to give abusers and pirates easy access to their product. With DRM, it only ends up hurting legitimate users while pirates illegally remove it. With GPL, it's not as clear-cut, but I'd imagine there are many projects who have used GPL'd code without releasing their source, while shops who abide by the license but don't want to release their code are forced to reinvent the wheel.
Again, I do appreciate your concern regarding code abuse. I certainly wouldn't like it if a company swiped by code and sold it as their own, but the chance of that happening is slim. I'm much more worried about the small startup who wants to use my library but doesn't want to release their code.
They only have to release their code if they are using someone else's GPL licenced code. They are totally free not to use GPL licenced code, we can argue the semantics of 'freedom' until the cows come home but nobody is forced to use someone elses GPL licenced code.
>A BSD license benefits the market and end user,
It benefits the proprietary market, and if you want your code to be able to be used in proprietary projects then yes, BSD is indeed a great choice. I don't see how the end user is better served by BSD than GPL.
However, many developers pouring hundreds of hours into code they then release as open source do not have any intention of having that code end up in proprietary projects. They want the code to remain open so that they as end users will be able to recieve any enhacements done to their source code. And given the vast popularity of the GPL licence, particularly for open source applications then I'd say it's serving it's purpose.
And don't take me wrong, I think programmers releasing BSD licenced code are extremely generous, and I personally think BSD/MIT style licenced code is a better choice for single purpose library/framework/component style code where there's little risk of proprietary forks.
At the end of the day GPL is about the source code and any further enhancements to it being made available to recipients, and this is what has made it so popular. And while that means it can't be used by proprietary code projects, we have ample proof that it's a licence through which lots of companies chose to cooperatively develop open source code, likely due to the very fact that all distributors of that source code is legally bound to release any enhancements.
It certainly places conditions on the use of code which has been released under it, but it doesn't take away the choice to not use that code.
The disagreement is not about how to best make sure the four Freedoms are respected, it's not about implementation. It's about whether the Freedoms are Freedoms at all. That tends to get lost when all everyone always talks about is licenses (i.e. implementation details).
No, I can't. I fundamentally don't understand why you would keep source code secret, why you would deny me the right to change it or to redistribute copies. It's utterly incomprehensible to me.
On the contrary, I believe the burden of proof as to why we should deny people these Freedoms lies on the side of the advocates or proprietary software, and thus far I haven't seen any compelling argument.
When I open an ice cream parlor you don’t have a right to know my recipe†. Why does that change with software?
Your argumentative work has to start there. You can’t just steamroll critics by saying “But the Freedoms are and should be Freedoms”.
—
† That right is of course limited: My right to keep the recipe secret is not absolute. I have to adhere to certain health and safety regulations, being able to keep the recipe secret does not override those regulations.
You can draw a parallel to physical goods: everybody has the right to do whatever they want with whatever they've bought. However, this does not translate to being able to sell that thing to somebody else while restricting what that person can do with it. You do not have the right to restrict what people do with things you used to own.
Suppose there's a work X licensed under the GPL. You've assumed that if I create a derivative work Y, then everyone else has an automatic right to Y. If I were to restrict Y, I'd be taking away this right, and so the GPL stops me from restricting it. In fact, it severely limits what I can do with my code, but enforces everyone else's freedom to use my code.
Let us assume the opposite: that a work does not belong to the public domain until its creator chooses to share it. Then any work X that has already been shared is fully protected (by any free software license). If I create a derivative work Y and keep it secret, I in no way limit people's use of X, so I have not violated any of their rights. Similarly, if I make a restrictive license on Y, I still haven't violated their rights. They never yet had a right to Y, only to X. In this case, the GPL is violating my rights to do as I choose with my personal work, Y.
So we have two opposing assumptions and two different conclusions: If you think a work you create immediately "belongs" to the public, then the GPL protects people's rights; if you think it "belongs" to its creator until shared, then the GPL violates people's rights.
I myself am in the second camp, so I think that the GPL does not technically qualify as a fully free software license. Perhaps the distinction could be phrased this way: I believe that a potential author of a piece of code should be able to do whatever they want with it, while the GPL is predicated upon the belief that all potential -users- of a piece of code should be able to do whatever they want with it.
But I don't think you can have both. You either have to allow restriction of the users' options (if the author so chooses), or you have to restrict the author's options.
Like their sizable contributions to LLVM, which is NCSA-licensed. Or their whole-cloth release of Darwin under the APSL (a license that even the FSF agrees fits their definition of 'free'). Or their release of Bonjour (wholly in-house development, if I'm not mistaken) under the Apache license.
Secondly, he does not believe that certain classes of software (like in your microwave) need to be free because they are basically part of the hardware. I imagine that if he owns a car, it only has low-level control software for the engine which is basically the same but not, say, a proprietary GPS system.
In planes it is again not an issue: he doesn't own the plane, so even if it had fully free software he would not benefit. I imagine if he ever did get a plane, he would want one with free software, but that isn't particularly pertinent since he will never buy a plane.
So the things you pointed out are not infringements of his rights--they're infringements of the rights of the manufacturer or the plane company. Stallman tries to persuade people like that to stand up for their rights, but that is all he does.
My response: "Is forced to compromise in the following cases"
I don't know how you managed to form your bizarre interpretation of what I said. I like the guy. I admire his ideals and approach and agree with his goals.