> Why would you let someone make a closed source version of your open source video editor?
How is that a bad thing? I think that's a zero sum game way of looking at it.
No damage is done if someone makes a closed source version. They can add value and stimulate competition. More often, they fail.
Occasionally, core developers may enrich and provide additional functionality upon a permissive core. Why not look at Postgres as an example?
And what harm is done? Lost code contributions? Some have no interest in collaborating on software they can't incorporate / copy from later without restriction. It takes time to wrap ones brain around a codebase.
Why would someone take time to understand the internals of a GPLv3 app, when they could never incorporate pieces of it in their code later on?
> it's ideal for applications like this.
Ideal is subjective. Judging by the above, it seems as if enforcing envy trumps programmers doing as they wish with the code.
> Why would someone take time to understand the internals of a GPLv3 app, when they could never incorporate pieces of it in their code later on?
...to make it better for their uses, rather than their products? "Enforcing envy," though--please, be more of a jerk.
I'm curious as to what large-scale applications have you developed and released under a permissive license that make you such an authority on what others should do with tens of thousands of their man-hours.
If there is no damage done when someone makes a closed source version, then there is no damage done when some pirates that closed source version. Some have no interest in paying for the closed sourced version anyway, and why should the closed source developer enforce his envy against users doing as they wish with the code?
How is that a bad thing? I think that's a zero sum game way of looking at it.
No damage is done if someone makes a closed source version. They can add value and stimulate competition. More often, they fail.
Occasionally, core developers may enrich and provide additional functionality upon a permissive core. Why not look at Postgres as an example?
And what harm is done? Lost code contributions? Some have no interest in collaborating on software they can't incorporate / copy from later without restriction. It takes time to wrap ones brain around a codebase.
Why would someone take time to understand the internals of a GPLv3 app, when they could never incorporate pieces of it in their code later on?
> it's ideal for applications like this.
Ideal is subjective. Judging by the above, it seems as if enforcing envy trumps programmers doing as they wish with the code.