Earlier quoted context omitted.
> It's a license that's misleadingly almost-free. Like the GPL is misleadingly almost free? As in it's free but if you release software which uses GPL software, it is under GPL? I am not arguing about the meaning of free, I am arguing against your "it's a license that's misleadingly almost free". Just like GPL's terms doesn't make it non-free, "don't use it for evil" doesn't make it non-free. EDIT: I see people argui…
On the terminology side: language is about communication, and there is a broad consensus on the meaning of "free" in terms of free software, exemplarized by the FSF's defnition, the OSI open source definition, and the DFSG. None of these definitions is identical to the others, and no doubt there are edge cases that would fall under one but not another, but neither the GPL nor Crockford's license is one of them; under…
So what is he supposed to do? His options are either use the MIT license unchanged, or invent his own? He liked the MIT license, and he wanted to add one of his own conditions. It's as simple as that.
As another commenter pointed out, the cognitive dissonance is the free software community is mind blowing. We are all for freedom and choice, as long as you are playing by our rules. We are against regulation, but only bad regulations. Ours are meant to do good and you are supposed to follow them.