Hacker News new | past | comments | ask | show | jobs | submit login

Question: Why do you choose LGPL-3.0? For many, one of the most attractive features of SQLite is its license (or should I say lack thereof).

I realise some people view public domain as legally problematic. I think the best answer for that is public-domain equivalent licenses such as 0BSD [0] or MIT-0 [1] – technically still copyrighted, but effectively not, since they let you do anything under zero conditions. (There are other, possibly more well-known options such as Unlicense or WTFPL or CC0; however, those tend to upset lawyers more than 0BSD and MIT-0 do.)

Of course, it is your work, and you are free to license it however you like. Still, some potential users are going to be put off by the licensing.

[0] https://opensource.org/license/0bsd/

[1] https://opensource.org/license/mit-0/




SQLite extensions are mostly meant to be dynamically linked, so the LGPL is entirely appropriate, IMO.

If anything I'd ask for an exception to allow statically linking unmodified builds (e.g. my use case, WASM, requires static linking all extensions).

Or a dual MPL+LGPL license.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: