3 ms·
Sure you could. Pay for a commercial license. Corporations pay for those all the time, and usually don't even get source.
by danjoc 10y ago
Sure you could. Pay for a commercial license. Corporations pay for those all the time, and usually don't even get source.
- tracker1 10y agoAnd that's worked out horribly for maintainers.. it's the whole reason for open-source. Look there are plenty of use cases where (A)GPL is perfectly suitable... a front end gui framework is not a good example imho. I've used plenty of closed source tools in the past... and they've always bit me in the ass at some point. I'd rather roll/adapt my own, or use something with a permissive license I don't have to worry about. I participate in the broader community, and prefer ISC/MIT licensing for most of what I do and use. If it's a given database server, sure, AGPL is fine as long as the client library is permissive.