It was also widely known for many years before Redis was a thing, i remember Slashdot comments from early 2000s about how BSD proponents are taken advantage of and they seem to like that whereas GPL proponents are taken advantage of as much as they take advantage those who take advantage of them (weird phrasing because the original quote i remember was a bit more explicit).
So it isn't really something you only knew in hindsight, it is also something that comes by ignoring people who were warning you about the consequences of your choice (royal you here).
> 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.
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.
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.
Yes, choosing overly permissible licenses (non-GPL OSS ones, in particular) contaminates the market for other software projects operating in that market.
Reciprocal licenses work like herd immunity: you need a large enough ecosystem to effectively keep freeloaders at bay while rewarding those who cooperate often.
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.
No, Linux is GPL licensed, it's not a naive permissive license.
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. However, in many cases, it's not the obvious decision for reasons related to the project's genesis (e.g. Spark or Mesos being student projects), and in others, it's not the route taken because of an idealistic impulse that I think would be really unfortunate to see squashed.