3 ms·
If you're going to the trouble of building a proprietary derivative, you are going to want to make sure no one but your paying customers can benefit.
by mcguire 8y ago
If you're going to the trouble of building a proprietary derivative, you are going to want to make sure no one but your paying customers can benefit.
- int_19h 8y agoYes, and that is achieved by keeping the part that makes it all sellable to consumers proprietary. But there's not much point in doing that with the backing open source libraries, especially if they're popular and in active development - maintaining a constantly diverging in-house fork is very time-consuming and expensive, so it must have some really big value-add to justify them. How many closed-source projects use, say, SQLite? How many of them fork it?
- mcguire 8y agoHow many contribute back to it? Would we know if they forked it?