So basically, there are both people who enjoy this kind of thought and people who vehemently oppose it on HN. We can see it easily in HN's comments.
So basically, there are both people who enjoy this kind of thought and people who vehemently oppose it on HN. We can see it easily in HN's comments.
Your computer is the factory. The binaries running on your computer are the means of production. You use your factory to do office work, for example writing documents, whatever. Copyleft is all about protecting the user that is running the binaries.
Now, if you control the source code to your computer, you control the binaries. This means that you control (own) the means of production, as far as a binary can be owned.
However, if you don't have the source code, I can sell you binaries but you have no mechanism to control your own means of production. Really, you haven't bought the software from me, you have bought a license to use it. It's as if you work in a factory, and you have to pay someone else for the privilege to use the machines in it.
Copyleft makes source code public among its recipients, meaning that control / ownership is shared, and you can still do what you want on your own machine.
Copyleft depends on copyright law to ensure public ownership; if all RMS wanted was a lack of ownership, as opposed to public ownership, he would promote public domain and BSD code.
Note that at no point here have I said that public ownership is bad - there are cases where it makes a lot of sense - but I do believe its not helpful to deny that the model is fundamentally socialist, as opposed to the EULA model which is fundamentally capitalist.
I still wouldn't call your conceptualization of Copyleft "socialism," because that (at least currently) has a strong connotation of government-involvement nowadays. I'd probably call what you're describing communism.
Anyway, thanks for listening. You could also argue that the source code was the means of production (of binaries, and then of work), which might be more accurate. I do not know much about Marx or the history of communism, but the focus on social concerns in the GPL is similar.
I get the analogy but I don't think it draws a reasonable comparison because it confuses the software with the license. The confusion is understandable because proprietary companies deliberately spread it. They want to blur the line between software and license so people have a harder time understanding their politics. But like you said, the software is not the product, the license is the product. Proprietary licenses aren't about restricting someone's ability to sell licenses, it's about keeping you from using their sales pitch. Copyleft is about making sure that no one can stifle anyone else's ability to use a certain sales pitch.
I'm not assuming I don't control my computer (it's mine to burn), I'm assuming I don't control the specific binaries on my computer unless I have the source code to them.
But, the amount of capital required to produce a binary of OS X or Windows is beyond anything you or I or the vast majority of users will obtain in the forseeable future, compared to a Debian binary which we could do today.
It's true that some people have definitely tried to write programs in their own languages with their own secret compilers just to make things even more difficult for potential copyright infringers, but thankfully that practice is not common because it has way more drawbacks than it does advantages.
That's fair. I have this romantic view that there's a brand of ethical/hacker startup, but that's, of course, without data to back up that not everything goes to shit when you have demands for meteoric growth.