3 ms·
Why not? It is basically a public domain license, it just uses more colorful language. IANAL, but I see no problem using such code in corporate environment. Wha
by annnnd 10y ago
Why not? It is basically a public domain license, it just uses more colorful language. IANAL, but I see no problem using such code in corporate environment. What are the risks?
- ptaipale 10y agoYANAL, and IANAL, but those who are, are always suspicious of modified license texts. They always fear there's a hidden catch that the language (colourful or not) tries to hide and get you tricked. And they are not entirely unjustified to do so. Also, in a corporate environment, there's typically some additional overhead cost and bureaucracy and approvals that a new license text brings in, even when the engineers and lawyers manage to agree everything is OK.
- viraptor 10y agoI don't think there's a problem. The situation I experienced is just that standard OSI licenses are preapproved. Anything else needs to go via manual process which takes days/weeks. So even if you say "do whatever you want", it's not a standard OSI license which means I have to get a confirmation first. And if I can find/write an alternative quicker, I will.
- kuschku 10y agoThere actually is a problem: There’s countries where "public domain" is not a thing, so the WTFPL becomes legally the same as "all rights reserved". Which is a problem.
- halomru 10y agoIt's very unclear how it works around the world in different legal systems. In comparison the CC0 spends a lot of words to work with all the jurisdictions where you can't legally give up all rights over a work. If you are operating internationally (like nearly the entire tech industry), complying in as many jurisdictions as possible is very valuable
- jcranmer 10y agoWTFPL lacks a disclaimer of the implied warrant of merchantability. If you're the author of such code, you could be sued for damages if there is a bug in it.