Even such a license gives legitimacy to the copyright regime. If you want others who are concerned about copyright to use your code I suggest MIT license. If you don't care about copyright for a project but you still want to share your code/ideas don't license at all.
> 0. You just DO WHAT THE FUCK YOU WANT TO.
What exactly is "what the fuck" legally speaking? Is it telling me I can use it in any kind of code base or does that pertain to copying and sharing? "Want to" , to/with what? My life? Career choices? The code base? The vagueness gives uncertainty. A license document has to give specific and explicit assurances. Sounding cool isn't good enough.
You claim it gives legitimacy to copyright regime but then go on to show exactly how it subverts the requirements of a license to be usable (clear, unambiguous, etc). You even finish it off by saying it's not good enough.
That is exactly what DO WHAT THE FUCK YOU WANT means. Interpret however, and consequently, do whatever to it. You want to complicate it and try to nail down what things mean, that's your prerogative. It doesn't try to be a legit member of the copyright license regime.
From the perspective of people who care about copyright, it means nothing. For those who don't, it makes no difference. Maybe as a statement that you're edgy or something.
3 comments
[ 3.1 ms ] story [ 19.3 ms ] thread> 0. You just DO WHAT THE FUCK YOU WANT TO.
What exactly is "what the fuck" legally speaking? Is it telling me I can use it in any kind of code base or does that pertain to copying and sharing? "Want to" , to/with what? My life? Career choices? The code base? The vagueness gives uncertainty. A license document has to give specific and explicit assurances. Sounding cool isn't good enough.
That is exactly what DO WHAT THE FUCK YOU WANT means. Interpret however, and consequently, do whatever to it. You want to complicate it and try to nail down what things mean, that's your prerogative. It doesn't try to be a legit member of the copyright license regime.