3 ms·
> I do worry that the dual licensing approach might turn off some readers I've not read any of your books (I tend to first look on O'Reilly Learning when I nee
by tzs 5y ago
> I do worry that the dual licensing approach might turn off some readers
I've not read any of your books (I tend to first look on O'Reilly Learning when I need a book on a given topic, and so far when I've needed a book on a topic you have written on I've found a satisfactory book there) so maybe it will be different for your readers, but that approach would definitely turn me off.
I buy (or read via a subscription service like O'Reilly) books to learn, not to obtain a code library. If I learn something from the book, even if that happens to be in the form of code, I want to be able to treat it the same way as I do things I learned from my college textbooks.
I don't want to have to be remembering that this thing I learned from that book can't be used on these projects because I don't have the right kind of license.
I'd be OK with it if the code that is actually in the text of the book is public domain or under a permissive license and the author includes a link to download more extensive code that is not under such a license, as long as the code in the text of the book is sufficient for learning the material the book purports to teach.
- EarlKing 5y ago> I don't want to have to be remembering that this thing I learned from that book can't be used on these projects because I don't have the right kind of license. You don't have to. "This thing you remember" is an idea, and ideas are not subject to copyright, only expressions. Unless you're copy-pasting something out of a book this is a literal non-issue... and if you are in fact copy-pasting then frankly you deserve it since copy-pasting is the nadir of engineering practice. It is literally you turning your brain off and ingesting someone else's mistakes. Don't do that. Textbooks are for learning ideas, not lifting code.