Live data from Hacker News

SDSL – Succinct Data Structure Library for C++

github.com

1–10 of 41 posts

Re: SDSL – Succinct Data Structure Library for C++

#3

Very nice! Why did you choose GPLv3 instead of LGPLv3?

The library is very template heavy and thus most of the code is in the header files so I guess it wouldn't change much in this case?

Additionally, we (the main authors) have lots of contributions from other researchers which we would ask for permission to the change the license (I think?).

Re: SDSL – Succinct Data Structure Library for C++

#4
post #3

Very nice! Why did you choose GPLv3 instead of LGPLv3?

The library is very template heavy and thus most of the code is in the header files so I guess it wouldn't change much in this case? Additionally, we (the main authors) have lots of contributions from other researchers which we would ask for permission to the change the license (I think?).

Also, using GPL for a library is often the better choice!

Many people believe that GPL is for programs and LGPL for libraries - as if the "L" would stand for "Library". But that's wrong! This was never the intention. The "L" stands for "Lesser" and means less protection than GPL, for very special circumstances.

According to FSF, you should use LGPL only for libraries that are competing with widely accepted proprietary libraries. For anything new and original, you should use GPL - to promote Free Software.

"Why you shouldn't use the Lesser GPL for your next library"

https://www.gnu.org/licenses/why-not-lgpl.en.html

(I disagree with that article in one point: If you compete with pervasive software, use a simple license like ISC/MIT/BSD rather than LGPL, to promote their usage even more.)

Re: SDSL – Succinct Data Structure Library for C++

#5
post #4
post #3

Earlier quoted context omitted.

The library is very template heavy and thus most of the code is in the header files so I guess it wouldn't change much in this case? Additionally, we (the main authors) have lots of contributions from other researchers which we would ask for permission to the change the license (I think?).

Also, using GPL for a library is often the better choice! Many people believe that GPL is for programs and LGPL for libraries - as if the "L" would stand for "Library". But that's wrong! This was never the intention. The "L" stands for "Lesser" and means less protection than GPL, for very special circumstances. According to FSF, you should use LGPL only for libraries that are competing with widely accepted proprietar…

Thanks for clarifying this.

Re: SDSL – Succinct Data Structure Library for C++

#7
post #6

Very nice! Why did you choose GPLv3 instead of LGPLv3?

Why not the MIT or BSD license? It would be more useful for other developers.

I beg to differ. I'm always happy to use external GPL libraries as an excuse for making stuff Open Source. Whenever I talked to unsure customers or managers, this was the single most convincing argument.

Of course, this only works if people aren't strictly against creating Free Software, but in that case you have lost anyway.

Re: SDSL – Succinct Data Structure Library for C++

#9
post #7
post #6

Earlier quoted context omitted.

Why not the MIT or BSD license? It would be more useful for other developers.

I beg to differ. I'm always happy to use external GPL libraries as an excuse for making stuff Open Source. Whenever I talked to unsure customers or managers, this was the single most convincing argument. Of course, this only works if people aren't strictly against creating Free Software, but in that case you have lost anyway.

So you actively use the viral aspect of the GPL to make more stuff Open Source. Probably what Stallman intended. :)
Post reply on HN