Hacker News new | ask | show | jobs
by mavelikara 2576 days ago
Amazon is, in effect, bringing attention to this issue and I am glad that they are.

> What you say ("The whole point of choosing a permissive license is that you want others to have the right to profit off of your work and give you nothing in return.") is obvious in hindsight, and should go without saying if you start a project with the express intent of commercializing it.

Even if you do thoughtfully choose a license with the express intent of commercializing the work, some competing project elsewhere - student projects, in your example - will eat your market. It is about time players entering our industry be warned of the effects of such "pissing-in-the-pool" activities.

2 comments

> some competing project elsewhere - student projects, in your example - will eat your market.

If a student somewhere is willing to do the same thing as your company for free and release their work under MIT, why is that a problem?

This smacks to me of Microsoft complaining that projects like Linux shouldn't be allowed to exist, because its unreasonable to expect them to compete with free.

If eventually we get into a state where Open Source development really isn't viable, then people will stop doing it, fewer people will be eating your market, and then Source Available projects will become commercially viable.

> If a student somewhere is willing to do the same thing as your company for free and release their work under MIT, why is that a problem?

There isn't a problem with that. The problem is when such projects aspire to commercialize their work, find it hard, and then complain when other commercial entities exploit their work.

The hypocrisy I am pointing out is that to get a software adopted initially projects choose overly permissible licenses; then when they try to monetize the project, they run into issues and cry foul.

"exploit", you need the quotes because nothing was exploited. Someone else was able to execute better than you were, that isn't a crime.
Are you saying that choosing a permissive license is like "pissing-in-the-pool"? As if do so contaminates the market for everyone?
> Are you saying that choosing a permissive license is like "pissing-in-the-pool"?

Yes, choosing overly permissible licenses (non-GPL OSS ones, in particular) contaminates the market for other software projects operating in that market.

Yes. The whole AWS problem stems from having too much software under "permissive" licenses and now enough under reciprocal licenses.

Reciprocal licenses work like herd immunity: you need a large enough ecosystem to effectively keep freeloaders at bay while rewarding those who cooperate often.

How would less permissive software existing have helped e.g. MongoDB with their "AWS problem"?
MongoDB did not have an "AWS problem". AWS did not release anything related to MongoDB until after they stopped making open-source releases.

MongoDB had a "We gave others freedoms we didn't like" problem, so they rescinded those freedoms. Freedoms that they'd given in the first place to profit off of the reputation of Open Source Software. If they'd never given those freedoms out, they'd never have had any problems.