2 ms·
Yes, the conclusion feels like a letdown. With the title of his post ("post copyright") you might think he'd have something to say about releasing code into the
by tjaerv 13y ago
Yes, the conclusion feels like a letdown. With the title of his post ("post copyright") you might think he'd have something to say about releasing code into the public domain, yet there's no mention at all of this. How is licensing your code under the copyright monopoly supposed to be "post copyright"?
The introduction at http://unlicense.org http://unlicense.org seems spot on for the topic of the blog post:
Why use the Unlicense? Because you have more important things to do
than enriching lawyers or imposing petty restrictions on users of your
code. How often have you passed up on utilizing and contributing to a
great software library just because its open source license was not
compatible with your own preferred flavor of open source? How many
precious hours of your life have you spent deliberating how to license
your software or worrying about licensing compatibility with other
software? You will never get those hours back, but here's your chance
to start cutting your losses. Life's too short, let's get back to
coding.
- the_mitsuhiko 13y ago> you might think he'd have something to say about releasing code into the public domain Author of the post here. I'm Austrian - the whole concept of public domain does not even exist in my legislation. I cannot legally waive copyright currently. The closest to putting code into the public domain is probably something like the WTFPL but I am perfectly fine with my stuff having a few more restrictions through the MIT/BSD to avoid license confusion. > How is licensing your code under the copyright monopoly supposed to be "post copyright"? It is not. However there is a certain trend ongoing that people wish the whole copyright system would be reformed and that would have more impact on Copyleft licenses than MIT/BSD. Aside from all of that I don't want to make license decisions for other people. :-)