>, but it may be interesting to create a new license to protect against this for new OSS projects.
Well, you also have to take the game theory of incentives into account.
Let's say you develop a new database called NextGenCockroachDB with a required 30% royalty license. That type of license will alter the behavior of people evaluating it and may very well prevent it from being adopted at all. If there's no critical mass of the market using it, the 30% royalty becomes a moot point.
The whole market of choices available to economic participants has to be analyzed. If potential buyers have an option to substitute a db with 30% fee with another open source db with $0 license, they will be incentivized to avoid paying 30%.
If an open source db requires royalty payments from cloud platforms, it will need to have amazing technology that nobody else can duplicate.
And even if you have some tech advantage, it still needs to compete with 0 cost license + increased infrastructure (since licensing dollars can now be spent on more hardware; 30% more hardware is hard to beat).
Well, you also have to take the game theory of incentives into account.
Let's say you develop a new database called NextGenCockroachDB with a required 30% royalty license. That type of license will alter the behavior of people evaluating it and may very well prevent it from being adopted at all. If there's no critical mass of the market using it, the 30% royalty becomes a moot point.
The whole market of choices available to economic participants has to be analyzed. If potential buyers have an option to substitute a db with 30% fee with another open source db with $0 license, they will be incentivized to avoid paying 30%.
If an open source db requires royalty payments from cloud platforms, it will need to have amazing technology that nobody else can duplicate.