Re:Why Greet Apple's Swift 2.0 With Open Arms?
by jahewson on Thursday June 18, 2015 @11:30AM
(#9739182)
That's not what he said though, was it? The complaint was that the GPL would force his users to share back, which is true.
[ Parent
| on HN ]
Re:Why Greet Apple's Swift 2.0 With Open Arms?
by icebraining on Thursday June 18, 2015 @11:49AM
(#9739349)
But that's the thing: it doesn't. You can take GPL'd code, modify it, give your derivative work to other people and never contribute back.
Re:Why Greet Apple's Swift 2.0 With Open Arms?
by ascagnel_ on Thursday June 18, 2015 @01:12PM
(#9740101)
You don't have to "give back" (push your changes back upstream), but you do need to put your changes out there to comply with the license once you begin distribution.
Re:Why Greet Apple's Swift 2.0 With Open Arms?
by icebraining on Thursday June 18, 2015 @02:49PM
(#9740794)
Not "out there," just to give the source to the receivers of binaries.
I know that in the context of B2C that sounds like an irrelevant distinction, but in B2B, it isn't - such software is often distributed only to a handful of organizations, who have no interest in becoming redistributers even if they have the right to do so.
I can tell you that there are lots of derivatives of copyleft software that are never made available to the original developers, in a perfectly legal way, and people who are choosing a license for their code should realize that.