CppCMS also offers commercial licensing. Don't get me wrong, I love BSD and MIT ...

CCs · on July 6, 2013

I really like the fact that Linux is GPL, the license served the community well. For large, stand alone apps it makes sense.

On the other hand I try to avoid GPL/LGPL for components.

Here is a scenario:

1. Invest in developing your app based on CppCMS

2. It takes off, great - buy commercial license.

3. The next version of LGPL gets more restrictive, you're stuck with commercial license.

4. Artyom gets hired by Google/Apple, no time for CppCMS anymore; only the LGPL fork gets fixes from now on.

5. Throw away your investment (time and money), start learning something else - how cool is that?

nitrogen · on July 6, 2013

That can happen with BSD software, too. Thr LGPL only gets more restrictive if the author releases a new version of their library that only permits the new LGPL version. Any project can change its licensing at any time, but with most open source licenses you retain your rights under the old license.

CCs · on July 8, 2013

Yes, it can happen with BSD and MIT. But at least you can start a fork from there, if you really have to. Forking LGPL stays LGPL, with the limitations & all.

interpol_p · on July 6, 2013

I like to release my libraries and tools under the BSD license, and I like to use others' permissively licensed libraries and tools in my own proprietary/commercial/closed applications.

greyfade · on July 6, 2013

LGPL doesn't stop that. You can still distribute your own source under your preferred BSD license. And if you link dynamically, the LGPL can't impose its requirements on your code.

The LGPL only requires that binary distributions of the derivative work have source reasonably available and that the library can be switched for another version by an end-user.