3 ms·

Deno is licensed as MIT. Awesome! But how will they prevent from being freeloaded? My sense is that GPL3 gets a ton of criticism on HN, but isn't it the perfec

Deno is licensed as MIT. Awesome! But how will they prevent from being freeloaded? My sense is that GPL3 gets a ton of criticism on HN, but isn't it the perfect defense against freeloaders? * license the code for proprietary use in your stack * use GPL3 if you have a non-commercial use, and are willing to accept the requirement to open source your own code. I don't understand why this option isn't used more by open source projects that want to be able to fund themselves. Can anyone explain? (Even better if there are examples / case studies)

jen20 6y ago
> I don't understand why this option isn't used more by open source projects that want to be able to fund themselves. One possible reason is that such dual licensing requires copyright assignment from external contributors.
breck 6y ago
The best IMO is to go public domain. SQLite is a great example: (https://sqlite.org/copyright.html https://sqlite.org/copyright.html).
- hu3 6y ago
  SQLite's case is super interesting. It is said that they can get away with having it as Public Domain because a key part of their business is SQLite's reliability which is asserted by their large and closed source test codebase.
  - breck 6y ago
    > which is asserted by their large and closed source test codebase. Oh I didn't know (or forgot about) this! Super interesting. I love that strategy. That's competition at its best. Don't assert any control over someone else, but do keep a few secrets to yourself so people know to come to you for the best stuff.