If you don't like Crockford's license you are at liberty to write that code yourself. Please don't call people who contribute a great deal to advancing computing (Free Software or not) names like 'harmful to Free Software'.
Even if there is genuine concern in the license and its usage in Free Software, it should be raised by pointing to the code and the license, not by making a personal attack.
Articles like this are harmful to Free Software because it discourages people from contributing. Not Douglas Crockford's license written in good humour and with nice intentions.
The article was itself childish, but then again, it's a personal blog, not some kind of official statement.
> it discourages people from contributing
True, but my perspective is different - what discourages people from contributing are ego-driven testosterone-filled spoiled brats. Incidentally that's why we also have so few women contributing.
Indeed, I would go further and say that the fruits of Open Source are in significant part the result of young men trying to impress and outdo each other in mental contests and show each other who's smarter (aka whose organ is bigger). This kind of competition is driven by testosterone.
And we all benefit as a result.
Please name a case.
Name one single case where this holds true.
> True, but my perspective is different - what discourages people from contributing are ego-driven testosterone-filled spoiled brats. Incidentally that's why we also have so few women contributing.
Ego and Testosterone in the same sentence - that has to be bad! But it is a different conversation altogether.
Could clauses like these get you the author in legal trouble? Or it's just you the incautious users?
This only leads to more fragmentation and bad relations between Debian and upstream.
It's no different with using commercial code that was licensed to you, anyway. You still have to adhere to the licensing terms and if you don't they can sue you.
I think maybe I'll switch to an AGPLv3 license with a no-evil modification for my future personal projects...
No one is stopping some dude from taking a large chunk of MIT or BSD licensed code modifying it and then closing it off forever. That fork could become the one to use while the pre-forked one dies in a fire because the software is no longer compatible with the new shiny one with feature X. "Oh crap! I'd like to fix this bug that's been plaguing me since I switched over to the closed source one, but now I can't." -- Some sorry dude who used BSD licensed software
Those who say they don't care about this sort of thing are lying to themselves and everyone listening.
There's this stigma around the FSF licenses, which has never made sense to me. The whole point of them is simply "I share with you, please have some common decency and share with me." This seems like common courtesy to me, and only fair. If some corporation really wants to close everything up, well the same logic for avoiding Crockford's license applies, just rewrite it and don't use it. But, he who shares should always win.
: yes, this was a loaded argument.
I sincerely like the GPL and AGPL. I don't think potential confusion is a compelling argument against either, nor do I think it against the "do no evil" clause.