3 ms·
I could be inclined to use GPL if I made some end user application rather than library code. Simply because I'd prefer the project not to be forked. If someone
by alkonaut 10y ago
I could be inclined to use GPL if I made some end user application rather than library code. Simply because I'd prefer the project not to be forked. If someone invents a great feature for my app, I'd like that to be either merged or killed, not merged into a fork.
The problem of the GPL is that it assumes that infinite forking of software is a good thing (more choice!) when the opposite is normally true - it's better to have ONE project that isn't perfect for anyone, but that is easy to find and actively maintained, than it is to have a large number of forks each with the pet feature of different users.
For library code it's a different story. If I write a library I'd hope to get commercial use of it. I suppose you could argue that in that case you should be using the LGPL rather than BSD/MIT/CDDL/Apache, but I honesly think the LGPL is underused simply because of it sounds a bit like GPL and it makes people nervous.
- icebraining 10y agoThe GPL doesn't prevent others from forking your project, we've seen quite a bit of hostile forks over the years.
- gribbly 10y ago>I could be inclined to use GPL if I made some end user application rather than library code. This very much mirrors my own preference. For popular end user applications there is a clear motive to do proprietary forks with extra features, which would lead to the original open project either lagging in features or having to spend effort in recreating the features of the proprietary fork while the latter can continously take any new features from the open project. For libraries/frameworks however, there is little if any real incentive for proprietary forks since it will be hard get developers buying into that.