Re:Immer: immutable and persistent data structures for C++
by ioquatix on Sunday November 27, 2016 @09:57PM
(#13053107)
GPL seems like a poor choice of license given the way the library would normally be used. What about switching to MIT?
[ Parent
| on HN ]
Re:Immer: immutable and persistent data structures for C++
by striking on Monday November 28, 2016 @12:19AM
(#13053573)
Or even LGPL, what copy-left libraries should be using.
Don't get me wrong, the GPL isn't the "worst thing ever" or a "virus", but I feel it's best suited to full applications rather than libraries.
Re:Immer: immutable and persistent data structures for C++
by mempko on Sunday November 27, 2016 @11:06PM
(#13053347)
We need more copyleft not less. I'm glad it is GPL and also plan to use it should I need immutable data structures.
Re:Immer: immutable and persistent data structures for C++
by gregburd on Monday November 28, 2016 @10:59AM
(#13056204)
Certainly copyleft has a place, but changing the license to LGPLv3 would allow this very useful library to be used much more broadly while continuing to require that improvements to the shared code be made public. If glibc were GPLv3 rather than LGPLv3 (same goes for Boost, etc.) almost no one would use it. IMO this library will either be re-written under a less restrictive license by some other author (wasting time and effort of the community) or migrate to a more open license (LGPL, ASLv2, MPLv2, MIT, etc.).
Re:Immer: immutable and persistent data structures for C++
by axman6 on Monday November 28, 2016 @12:24AM
(#13053583)
For something as fundamental as a container library, GPL will basically mean it's not used widely. There's a reason many language ecosystems generally use BSD/MIT licences for almost all libraries (haskell being just one example I know this to be true for). Applications may be another story.