[jefftk]

> Forget the courts for a second, just ask yourself what is the right thing to do

Forgetting the courts, whether reading the source code and learning from it is intended to count as "use" is not clear to me, and I would have guessed no. Using a tool and examining a tool are pretty different.

[godelski]

Context matters, right?

Human reading code? Ambiguous. But I think you're using it. Running code? Not ambiguous.

Machine processing code? I don't think that's ambiguous. It's using the code. A person is using the code to make their machine better.

This really isn't that hard.

Let's think about it this way. How do you use a book?

I think you need to be careful that you're not justifying the answer you want and instead are looking for what the right answer is. I'm saying this because you quoted me saying "what is right" and you just didn't address it. To quote Feynman (<- look, I cited my work. I fulfilled the MIT license obligations!)

  > The first principle is that you must not fool yourself, and you are the easiest person to fool.

[jefftk]

> How do you use a book?

I think that's a great example, actually! Imagine a book with a license saying that you could only read it if your goal was to promote the specific ideology, and quoting was only allowed to support that ideology. Reading it and then quoting it to debunk that ideology would be both legal and ethical.

With books, once you buy the copy you are free to read it, lend it, or resell it: a license can give you additional rights, but not restrict you further, nor should it.

> To quote Feynman (<- look, I cited my work. I fulfilled the MIT license obligations!)

Huh? Feynman didn't say that under MIT license.