2 ms·
> I don't think "being comfortable with being exploited" is a component of "being a big person". In the context of the types of projects I was imagining, a com
by Wowfunhappy 7y ago
> I don't think "being comfortable with being exploited" is a component of "being a big person".
In the context of the types of projects I was imagining, a company would likely just rewrite any code that wasn't available via MIT or similar. If I'm not getting anything in return either way, am I being exploited?
Logically, if the outcome is the same for me, there's no reason to make others redo work.
- jerf 7y agoThat's basically the logic I used too for my own code. As I hinted at but may not have been made clear, I was using "exploitation" quite deliberately as a loaded term in the beginning, only to try to defuse it in my final paragraphs as in many, perhaps even the vast majority, of cases you aren't really being that "exploited" no matter what anybody does. If somebody outright stole any of my projects and claimed them as their own work, I still would honestly be only annoyed, and maybe make a few posts in my README.md about the situation, and move on with my life without even a thought about engaging the legal system or anything. But as rare as it may be, there have been many cases where an open source code base really was "exploited" by any reasonable sense of the term, with corporations slapping their logos on it and reselling significant works in violation of the license, and those cases are significant because of their size, even if they are rare.
- a1369209993 7y ago> there's no reason to make others redo work. As a simplified example, consider Corporation G and Corporation P. One will eventually lose market share to the other, go bankrupt, and be replaced by Corporation R that bases its business practices on the more successful one (then the cycle repeats). Both are evil, as corporations are wont to be, and in particular will never release anything under a less restrictive licence than they have to (so they will never release software under a MIT licence). However, G will release software under the GPL if this allows it to save work, whereas P will always release software under a proprietary licence, even if this forces it to expend more resources rewriting GPL functionality. Releasing code under the GPL exerts a selection effect that favors G over P, and in the long run results in corporations that release somewhat more software period - and significantly more software under FOSS licences - than if P was not forced to redo work.
- deleted 7y ago[deleted]