• 8 Posts
  • 104 Comments
Joined 10 months ago
cake
Cake day: September 23rd, 2023

help-circle




  • The author of JSLint wrote:
    "So I added one more line to my license, was that, “the Software shall be used for Good, not Evil.” And thought: I’ve done my job!
    /…/
    Also about once a year, I get a letter from a lawyer, every year a different lawyer, at a company. I don’t want to embarrass the company by saying their name, so I’ll just say their initials, “IBM,” saying that they want to use something that I wrote, 'cause I put this on everything I write now. They want to use something that I wrote and something that they wrote and they’re pretty sure they weren’t gonna use it for evil, but they couldn’t say for sure about their customers. So, could I give them a special license for that?

    So, of course!

    So I wrote back—this happened literally two weeks ago—I said, “I give permission to IBM, its customers, partners, and minions, to use JSLint for evil.” "



  • People seem to think that those who choose permissive licences don’t know what they’re doing. Software can be a gift to the world with no strings attached. A company “taking” your code is never taking it away from you, you still have all the code you wrote. Some people want this. MIT is not an incomplete GPL, it has its own reasons.

    For example, OpenBSD has as a project goal: “We want to make available source code that anyone can use for ANY PURPOSE, with no restrictions. We strive to make our software robust and secure, and encourage companies to use whichever pieces they want to.















  • I bet they considered the options. It could simply be that no one has had time to change the installer. It could also be that the people who care about free software to the degree that they want to avoid non-free firmware usually figure out how to do it, and that too many options confuse new users. I don’t know. A feature request discussion in the appropriate mailing list could be a good idea if you want change.