There are perfectly good licenses that do pretty much what the author seems to desire, but which are also legally sound. Inventing your own license, even if it’s just a few words, is bad practice (unless you’re a lawyer, but inventing another license is still questionable practice even then :P).
It’s certainly not universally agreed that you need those warranty disclaimers. Generally warranty disclaimers don’t work anyway. You can’t sign away your right to protection under New Zealand’s consumer guarantees act, and I imagine it’s similar in other countries: there’d be no point having warranties if they could just be ignored with a bit of caps lock.
More likely is that there’s just obviously no warranty because it’s not a product, it’s open source software.
If only it had a sane license… sigh
There are perfectly good licenses that do pretty much what the author seems to desire, but which are also legally sound. Inventing your own license, even if it’s just a few words, is bad practice (unless you’re a lawyer, but inventing another license is still questionable practice even then :P).
There was even a GitHub issue where someone tried to make them see how bad that was and that still didn’t work
It’s certainly not universally agreed that you need those warranty disclaimers. Generally warranty disclaimers don’t work anyway. You can’t sign away your right to protection under New Zealand’s consumer guarantees act, and I imagine it’s similar in other countries: there’d be no point having warranties if they could just be ignored with a bit of caps lock.
More likely is that there’s just obviously no warranty because it’s not a product, it’s open source software.
Oh wow, this was educational.
/me goes and fixes some of his WTFPL-licensed stuff
Thanks!
You’re welcome mate, and don’t worry. I think everyone had one of those “oh no what am I doing with all my projects” panic moments at some point
How mature is this implementation? The claims the Readme makes are pretty impressive but the documentation is hit or miss