And again. You're talking about tinkering. What about the freedom to run for any purpose? What about the fact that one is renting a proprietary service with a de facto universal backdoor and spyware capabilities? How is that not an ethical concern?
Voluntary association does tend to work in this case, but it doesn't change the fact that a party is engaging in unethical behavior. Furthermore, the ultimate end result of "Don't like it, don't use it" is the erosion of choice.
You are NOT required to use any proprietary software.
Oh, hell yes, you are. Government agencies, who have a duty to serve the public, run proprietary software all the time. Meaning they are deprived of computational sovereignty and cannot guarantee they are performing their duties unfettered. If you've been to public school in most countries, you are taught to use proprietary software in IT classes. An institution devoted to learning compels students to use software that explicitly forbids being learned from and studied. Even more harmful are proprietary formats, which are like a lock and time bomb on your data, yet are ubiquitous.
Network services are a big ethical dilemma of their own and yet practically unavoidable.
Software is essential to contemporary civilization, and you will be using lots of proprietary programs. You cannot reasonably expect people to become hermits over it.
It's the same logic as religion, who feels I shouldn't be allowed to marry someone of the same sex even though it doesn't affect them in any way.
What a load of nonsense. It is the proprietary software vendor who deprives users of freedom. Your analogy is backwards and completely inappropriate. Free software mandates you have the freedom to run the program for any purpose, so gay marriage would be unrestricted. Proprietary vendors would have terms that may or may not restrict it.
I applaud you taking the time to respond carefully like this. It's always nice to be reminded of the simple, yet powerful foundation at the heart of Free software: the four freedoms:
The freedom to run the program as you wish, for any purpose (freedom 0).
The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
The freedom to redistribute copies so you can help your neighbor (freedom 2).
The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.
Note that "access to the source code" is not one of the four freedoms -- it's merely a precondition to be able to satisfy them.
ed: It might be interesting to note, that most of these freedoms exist for physical objects: you are generally allowed to fix broken physical things, even those that are under patent protection. Or to make sure stuff fits where you need it. And you generally can sell/give away stuff you're not using. These rights are actually protected by law.
Free software could be viewed as a rather conservative measure towards ensuring that we get these "everyday" rights wrt software as well.
Actually, it's exactly the first freedom the one missing from physical objects. You are free to analyze Coke with a microscope, but you won't get the recipe. You are free to 3D-scan a fork and analyze its alloy, but you won't be given the original CAD project and the production plans for the material.
I'm not sure if you were implying that the 4F are replicating what happens with physical objects; I would disagree with this. The 4F expect from software much more than we expect from any other good or service we buy/rent/consume.
Ah, but there are multiple levels: You can take chair apart, or split your pants along the seams -- and if you can find a material with comparable strength, or a fabric you like -- you are free to make as many "copies" as you want.
You are free to attach a metal head to a shaft and call it a hammer, and look at other hammers for inspiration, if your hammer doesn't work quite right.
You are of course right that it only goes so far -- and this is perhaps most scary in the field of bioengineering -- with the possibility of a) sterile produce (you wouldn't be able to plant a potato any more), and b) patented/"copyrighted" gene sequences -- making it illegal to plant certain "proprietary" produce without a license grant.
I do agree that the analogy is flawed -- is the shape of a fork more like the api or the source code? I suppose the main difference is that many useful physical things are trivial conceptually (once you've had/seen the idea).
I'm talking about tinkering because that was the example I was responding to. I think your lack of logic in this thread is unethical. Saying so doesn't make it true though, does it? Actually, nothing you said is logical. You don't have to take a windows programming course, you can choose the many more nix based courses. Those are choices, along with my choice to use proprietary or open licences. You want to remove my ability to make that choice. Foss should exist, and so should proprietary. Anyone dictating that only one or the other should exist is an extremist.
Your arguments are framed as if to make them valid, but they are still fallacies. The MIT licence exists for a reason, and the reason it's the most commonly used. It's the non-extremist licence.
Anyway, I'm done. Arguing with extremists is a fools errand. I believe there is a place for all models.
Insisting people pass on the freedoms that they benefited from to other users, is not extremism. You have a chip on your shoulder.
You say that copyleft removes your freedom to choose to distribute a program as proprietary software. This is correct, but you portray it highly disingenuously, like it's an equally weighted choice.
Generally, freedom has the most influence when its recipients are those at a lower position of power. The power of the software vendor is to have full control over the usage of the program, ostensibly either to provide a better UX (which is dubious), to exercise their IP (an ethical landmine), to benefit from unsustainable per-unit business models that ignore software's intrinsically anti-rivalrous, non-scarce and intangible nature, or other reasons.
Let us see how the user is affected. And keep in mind, all programmers are users. Programmers will be using other people's software at dramatically higher quantities than they will ever write anything individually. As such, user freedom is of paramount importance to them.
Now, for a certain amount of convenience on part of the vendor, the user is put in a position where they cannot a) run the program for all purposes that they may desire to use it, b) study and change it to adjust it to their needs, c) share it with friends, neighbors and acquaintances and d) enrich their community by sharing modified copies. In other words, they get software without most of the benefits that actually comes with having things be software in the first place.
As such, the users lose individual and collective control for the benefit of the vendor, but at a deadweight loss for everyone else. Because, when the software leaves the vendor into another person's machine, how it's used is in no natural sense of any interest to them. Not anymore than a chef is interested in how other people use their recipe. This has been accepted as the first-sale doctrine by courts across the world.
I therefore conclude that user freedom should be given at all times where the software is user-facing.
You mean to say that the original developer who chose to release via MIT, gets exactly what they agreed to? God forbid, you're right, it's a whole moral catastrophe.
This is textbook nanny state drivel. You don't need to protect people from themselves. There are thousands of articles online, people can do the research. You aren't publishing anything without access to the internet, and the internet has more than enough articles and even wizards to help you choose.
No, those are absolutely real. It's not up to you to protect or stop it. It's a life lesson. It's the same as copyright. Every kid starts some project using someone else's IP. We see it daily. Then someone explains that you can't use Homer Simpson in your app. You don't abolish copyright because some kid gets a C&D.
Voluntary association does tend to work in this case, but it doesn't change the fact that a party is engaging in unethical behavior. Furthermore, the ultimate end result of "Don't like it, don't use it" is the erosion of choice.
You are NOT required to use any proprietary software.
Oh, hell yes, you are. Government agencies, who have a duty to serve the public, run proprietary software all the time. Meaning they are deprived of computational sovereignty and cannot guarantee they are performing their duties unfettered. If you've been to public school in most countries, you are taught to use proprietary software in IT classes. An institution devoted to learning compels students to use software that explicitly forbids being learned from and studied. Even more harmful are proprietary formats, which are like a lock and time bomb on your data, yet are ubiquitous.
Network services are a big ethical dilemma of their own and yet practically unavoidable.
Software is essential to contemporary civilization, and you will be using lots of proprietary programs. You cannot reasonably expect people to become hermits over it.
It's the same logic as religion, who feels I shouldn't be allowed to marry someone of the same sex even though it doesn't affect them in any way.
What a load of nonsense. It is the proprietary software vendor who deprives users of freedom. Your analogy is backwards and completely inappropriate. Free software mandates you have the freedom to run the program for any purpose, so gay marriage would be unrestricted. Proprietary vendors would have terms that may or may not restrict it.