The lesson is clear: if you want to win in the long run, you need not just great skills and tech, but you have to go public domain. Or to put it bluntly: #LicensesAreForLosers.
The lesson is clear: if you want to win in the long run, you need not just great skills and tech, but you have to go public domain. Or to put it bluntly: #LicensesAreForLosers.
Public domain raises all sorts of challenges for potential adopters of the software that aren't an issue with a more deliberately designed license.
UPDATE: I misremembered this. He does talk about some of the surprise challenges in this interview, but does not go as far as saying that he regretted it: https://changelog.com/podcast/201#transcript-215
""" “We’ll sell you a license for SQLite.”
We do our best to talk them out of it and explain they don’t need this, but for a lot of people it’s cheaper to pay the fee and get the license than it is to convince their lawyers that they don’t need one. """
Priceless! Except that it's not. LoL.
Proof:
For every pair {protocolX,protocolY} where functionality(protocolX) = functionality(protocolY) && isPublicDomain(protocolX) == true && isPublicDomain(protocolY) == false, then speedAndUtility(protocolX) >> speedAndUtility(protocolY).
This still doesn't add up to me.