|
|
|
|
|
by jheriko
3943 days ago
|
|
> very special circumstances. my experience is that these 'special' circumstances are pretty much "you need to use it in a proprietary production environment" and "you don't want to stop people using your software". this is close to what the FSF say so I don't think i'm far off the mark... the problem with GPL imo is that it is manifestly not free. you must abide by severe restrictions to use the code, which for a lot of software development would incur impractical costs. even if i want people to use my code for free I never use the full GPL license. i don't see any good reason to becasue i never want to dictate what other people can or can't do with their own software by virtue of having helped them out with mine. i really don't understand the sentiment... for example, the choice of GPL here means that nowhere i have ever worked would touch this officially. i can tell you that most of those places are also not thorough enough to stop some random wannabe hotshot programmer from stealing large swathes of code from this repo and using them anyway... (i do not endorse this practice - but i am perhaps a little bitter because i am usually the one who spots these things and has to deal with them). |
|
But to address one aspect, I do agree that I really don't understand the sentiment to dictate what other people can or can't do with their own software. Suing people for sharing software is wrong, and having EULA's that prevent people from understanding how their software operates is also wrong. The argument that you have to add proprietary licenses in order to earn a living is illogical and only create a world where people don't trust each other.