Hacker News new | past | comments | ask | show | jobs | submit login

This actually strikes at the heart of the disconnect between open source philosophy and common vernacular.

I've argued for years that "free" does NOT mean "free to use as long as you follow my restrictions". To me the only licenses that meet this criteria are the permissive ones such as MIT, BSD and friends where the only requirement is preservation of the copyright notice. The vast majority have limits of what you can do, or when you have to pay, or some other BS that just complicates everything and IMHO just reeks of "I'm manipulating the FOSS community so I can make a buck" or "I'm pretending to give this software away but actually have a laundry list of rules you have to live by". Basically the opposite of what "free" means!

Similarly, "open source" implies that I can do whatever I want, since it is "open". But most open source licenses - including this one - have restrictions and in many cases pretty strict ones that forbid use for many. This is not open at all.

Either give it away, or lock it up, but PLEASE PLEASE PLEASE stop with the hypocrisy, lying and wordplay so you can make a buck (or satisfy a religious tilt). If you want me to help you with your code then you gotta let me use it how I see fit!

And for the love of all things holy, quit calling restrictive licenses "free". This is a binary state, it is either free or non-free, and "you can only use this if you make less than X" or "only use this with other free software" or "if you make changes you have to share" are NOT FREE.

There. Thanks for reading. Stepping outside to yell at a cloud now. And get off my lawn.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: