> As soon as you leave this club and want to pull code from a GPL-licensed project into your MIT-licensed project, well, sorry, too bad for you.
So what? The GPL seems like a decently fair way of saying that "I'll make a contribution, as long as everyone else using it keeps making that same open contribution".
Personally, if I wanted to release open source code, I wouldn't want it to fall under an MIT license, because then some corp could simply take it and not make the same contribution back.
The author claims this "harms developers of non-GPL-licensed FOSS software" - give me a break. Does it break their legs? Give them the flu? It doesn't harm anyone. Maybe just inconveniences them. Cry me a river.
> As soon as you leave this club and want to pull code from a GPL-licensed project into your MIT-licensed project, well, sorry, too bad for you.
So what? The GPL seems like a decently fair way of saying that "I'll make a contribution, as long as everyone else using it keeps making that same open contribution".
Personally, if I wanted to release open source code, I wouldn't want it to fall under an MIT license, because then some corp could simply take it and not make the same contribution back.
The author claims this "harms developers of non-GPL-licensed FOSS software" - give me a break. Does it break their legs? Give them the flu? It doesn't harm anyone. Maybe just inconveniences them. Cry me a river.