Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> If you take all the books, then others can't enjoy them.

Sure, and if your company takes a bootstrapped commercial open source product that it didn't develop or contribute to, and then pays several employees a salary to do things which actively reduce that product's ability to develop a sustainable revenue stream, then you definitely risk permanently destroying that open source product.

On a macro level, if many companies do this, the entire ecosystem of open source begins to falter. Hence all the moves to BSL, SSPL, Commons Clause, etc.

I was making an analogy to that. If some people keep taking all the books and selling them, the system falls apart, and people stop putting free books in the box.

> it seems like you deliberately chose a license that allowed and encouraged exactly the behavior you saw.

"Allowed", yes. But nothing in the license I chose (Apache License v2) actively "encourages" the behavior of using a project in a way that actively destroys the project. (Nor does it discourage it either.)

> You're trying to make your project appealing to businesses by telling them they can take it for free and give nothing back. But you're also saying that behavior is "antisocial" and "completely destroys the offering/concept for everyone."

I have no problems with businesses using a project for free and giving nothing back, on its own. I do have a problem with businesses taking a project, and profiting off it while also directly competing with it and/or forking the project in a way that directly kneecaps the project's revenue stream. That is what I am calling antisocial and destructive.



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

Search: