Nobody's freedom is impeded. They didn't have the freedom to modify the code in the first place, since they didn't have the source code. Nothing they could do before has been taken away.
It's really intellectually dishonest to use this freedom and morality rhetoric when you're actually talking about compelling people to give away something they have created.
Not that I think it's conceptually a bad idea. I see nothing wrong with the idea of the GPL as a concept. A contract that says 'if you use this software, you agree to also give away any code you base on it' seems fine.
But I see no reason not to just call it 'permanenrly malleable' software or something like that.
It's the faulty rhetoric around freedom that is presented as a moral crusade that is a problem.
The GPL is instead defined on the tradition of positive liberty, which defines freedom as the number of options freely available to each person to choose. There's a very real risk of those being reduced by permissive licenses, as you can no longer ignore network effects, as negative freedom (being defined over individual atomic actions) does.
History shows us that if you allow open source code to be relicensed as proprietary, the competitive advantage of companies building and selling products with enhanced features tend to displace the original project, which gets abandoned. This happened to Unix, to Mac OS X, and is now happening to Android. If this continues for an extended time, the whole ecosystem evolves and the old software becomes unusable, greatly reducing the total options that users can effectively perform - not by an legal or coercive restriction, but because of pragmatic impossibility. There are permissive projects where this doesn't happen (at least for a while) because of the economic incentives of remaining close to the free+open project, but the risk is always there.
What good is the permission to run the original, abandoned version of a software project if all the available hardware has been locked and is uncapable of running it, and it's impossible to modify it to support the modern functions that are available in the proprietary platform and required for any productive usage? Those are very real threaths, and the GPL was designed to combat them (as a reaction to the first time they happened on a large scale). Avoiding this "reduced total available options" scenario is what GPL projects call freedom, not "reducing the number of restrictions" definition that you use. Not a problem of rhetoric, but of chosen vocabulary.
I also don't accept "history shows us" as establishing some law of nature when the history we're talking about is a couple of decades.
I think the abandoning of ecosystems can just as easily be explained by them being based on inadequate foundations, than by a mythical horde of developers somehow being prevented from working on them. Usually systems are abandoned because of a lack of economic incentive, after all the displacement you describe can only happen if proprietary development produces enhancements more efficiently than open source. Witness the failure of the Linux desktop.
I think 'greatly reducing the total options that users can effectively perform' is a statement that needs much more qualification. To me, that's a function of design, extensibility, and how much leverage a system provides, and is independent of whether the source is available or not. Extending by forking is a last resort.
Nevertheless, I do respect the hypothesis that a GPL style open system provides an important counterbalance to proprietary systems.
What I do not support is the dishonest use of language and morality to further it.
If you are using positive freedom, then there is much more to be gained through improvements in software design - e.g. along the lines of Alan Kay's FONC - to increase leverage - than through ideology.
I still fail to see what is it that you call dishonest use of language. If freely talking of one's perspective and goals is dishonest, then all ideologies are.
The dishonest use of language is the misappropriation of the word 'freedom', and the moralizing around what is essentially a business problem. But, if you are claiming to be an ideologue, then fair enough.
In which case, I'd love to hear more about how that ideology translates into a better future economic future for software developers. To me it seems to just translate into greater dependence on powerful corporations.
Not necessarily a bad thing (your product might be legitimately better), but it is a decrease in software freedom.
Forking FreeBSD is not remotely the same thing as forking OSX and you can't "just use the open-source alternative if they want to change the source code" of OSX.
I really don't like the idea of licences which compel their users to act in a certain way. Freedom cuts both ways.
OSX users do not have this freedom. Hence, prevalence of OSX reduces software freedom. Ability to choose between OSX and alternatives is something but it is not software freedom.
This doesn't follow. Like most arguments about proprietary software reducing, rather than not providing, software freedom, it seems to rest on the assumption that if proprietary software did not exist, it would be replaced use-for-use with Free software, that is, that license models have no impact on the creation or distribution of software.
If you stop using this misleading word, the whole GPL thing looks more reasonable, but also less like a moral crusade.
What business models for software do you prefer, and why?
I have no objection to "paid software" as a business model, because the term is too broad. Paying someone to add a feature I want to a GPL project and release the result is, I think, not something anyone would object to. I have objection to "proprietary software" as a business model, because it collapses the value that the software can provide; I am not convinced that this objection is sufficient to say that proprietary software is always the wrong choice. I have more objection to proprietary software where, having paid, I cannot see the source and make changes (or pay others to make changes).
There are a number of alternatives for funding development of mass-market software that are more compatible with copyleft licenses (donations, threshold pledge models, consulting) and I'm currently working on an innovative project in this space.
I do also not care if the legal violence happened because of changes an other developer did on my work. Just because they added something does not give them the right to use what I made into a legal weapon.
Eliminating the revenue from selling the same work multiple times is probable consequence of the FSF's mission. It is uncharitable to say that it is the FSF's mission. It is also false that this implies an hourly rate of $0.00 - there is a huge amount of programming work for which the first copy is the only copy, and that can be sold just as readily as ever in a world using even the strictest AGPL for everything. And that's not even considering donations, threshold pledge systems, &c.
Programmers are expected to work other jobs to subsidize their hobby. IIRC he also suggested that they could sell copies of their software on physical media, but this is irrelevant in the bittorrent era.
He acknowledges that realization of the FSF's goals would most likely end the phenomenon of professional developers and is perfectly okay with this.
It's somewhere on the Philosophy section of the gnu project's website. It's late, but I'll find the specific link later.
Your ad hominem, however, is misdirected. I too oppose FSF's mission to value our craft at $0.00/hour. People have the right to compensation when others enjoy their creative output and if that impedes software freedom, so be it. Software freedom is a good thing but by no means an inalienable right.
I support open source because it's in our collective interests to subsidize the creation of freely available and high-quality platforms/tools with our earnings from proprietary software. I don't think we'd have those earnings without proprietary software, though.
Some people point to the Red Hat model. But most people don't need those kinds of guarantees. Third parties (i.e. every system administrator who's ever been responsible for at least one CentOS box and is not a Red Hat employee) can provide good enough support for drastically cheaper because they don't have the extra costs associated with developing the product.
Without proprietary software, it is in no one's interest to make software. (Well, maybe for personal amusement.) Not even line-of-business software, because you're just handing your competitors the ability to undercut your prices and push you out of the market (similar productivity boost, lower costs than you).