Earlier quoted context omitted.
With the noise people make when you don't use an OSI open-source license, little wonder. But when Redis started I think we didn't yet boardly understand the limitations of OSI licenses in the era of big tech cloud computing. To people starting projects today, you have no excuse, we know better. Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. OSI Open-source business models…
> Don't use OSI open-source unless it's entirely a labor of love that you're giving away free. Well, know what your secret sauce is. I think performance is really the best differentiator. Make a fully behaviourally compatible (maybe not bug for bug) version available and then sell a proprietary faster version. Think an compiler that doesn't due any optimisation and outputs naive code. You know have a useful OSI proje…
and in effect GitLab is doing a BSL-like thing by after a few years they release features to the free tier
but it rarely works if you need to decline contribution from people who would eat into your profit margins. I think ElasticSearch had this problem (and the community basically ended up with a few forks, because people sent the patches for security features that were in the enterprise version, and to no one's surprise they did not get merged ...)
so, I guess it works if there's a huuuge scope with plenty of things to contribute, to shoot for the moon together, without hurting the business side too much.