3 ms·
When you own the entire vertical, all the way to end user, it makes sense. In practice, the final steps that are necessary to deliver something useful to the u
by int_19h 8y ago
When you own the entire vertical, all the way to end user, it makes sense.
In practice, the final steps that are necessary to deliver something useful to the user are often considered the most boring and tedious (UI, documentation etc), so many F/OSS projects either don't bother at all, or provide something half-baked. But if the underlying libraries allow for a proprietary derivative, then that might motivate some businesses to come and do all that tedious stuff for $$$. Such businesses might not contribute back much, but they are also unlikely to fork - less code to maintain that way.
When that happens, I don't think it's a loss for anybody, really. The open code stays open and can be improved further, and it also gets used by more people in better ways. Some would argue that library developers aren't properly compensated, but the act of voluntarily releasing something under a non-copyleft license is explicit consent to that.
In the hypothetical "suffering an annoying bug" scenario, I would, of course, prefer to have the source so that I can fix it. But if the real choice is between having a product with an annoying unfixable bug (but plenty of other added value), and not having one at all, because nobody wants to build my extremely useful GPL'd library into a polished product, the obvious pragmatic choice is the bug.
- mcguire 8y agoIf 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?