3 ms·

Less legalese, I'm here to write code, not interpret law. That's why I prefer the MIT license.

• Alupis 12y ago
  > Less legalese, I'm here to write code, not interpret law. Is reading/understanding the License one time really that difficult? After your first read through, you basically just copy a text file into the root of your repo for each project and you're done... For me, the license could be 1 paragraph or 1,000 pages. I only have to understand it once then it just becomes a standard part of any new repo I create.
  • Aldo_MX 12y ago
    You must remember that: a) Many people don't speak English natively. b) Jurisdictions are different in every country, and sometimes in every state, the law of where you live takes precedence over what your LICENSE file says. Ex. jurisdictions where encryption is forbidden. c) Some people just make projects "for fun". Reading and understanding different licenses until you find the one you agree the most with is definitely "not fun". d) Nobody recommends a license without a disclaimer of "at your own risk" unless that person is a lawyer and it's getting paid to do that recommendation.
  • bronson 12y ago
    ...until you want to integrate some code that's under a different license. Wading through pages of potential incompatibilities is not the way I want to spend my time. Speaking from experience here.
  • fnordfnordfnord 12y ago
    >Is reading/understanding the License one time really that difficult? Yeah, actually, it is. Otherwise, litigation over these matters wouldn't take months and tens or hundreds of thousands of dollars. >I only have to understand it once Sorry, but just let some judge/jury make a decision that changes or restricts the meaning of a word like "distribute" and you've potentially got a big job ahead of you.