11–20 of 45 posts
This is a potentially useful project but I could never use it for fear of "FuckItDB" appearing in an exception call trace that a client might see. Names don't have to mean anything, but certain names are still unacceptable.
Just wrap it with FuckIt.py (previously discussed at https://news.ycombinator.com/item?id=6858855 ) "to make sure your Python code runs whether it has any right to or not"
Earlier quoted context omitted.
Although the WTFPL website ( http://www.wtfpl.net/faq/ ) does note somewhat ominously that it hasn't been tested in courts, it seems legitimate enough to me. Is there any evidence outside of its lack of history in court that would indicate it isn't suitable for production use? EDIT: gnu.org also says "We do not recommend this license" ,pointing to the Apache license as providing better protection against 'patent trea…
Track down what 'DannyBee has to say about WTFPL and licenses like it. There are good reasons not to use it even if you don't care what happens with your code.
Earlier quoted context omitted.
Track down what 'DannyBee has to say about WTFPL and licenses like it. There are good reasons not to use it even if you don't care what happens with your code.
I believe this is what tptacek is referring to: https://news.ycombinator.com/item?id=8104407
I actually renamed it to 'butterdb' a while ago because some people found fuckitdb hard to swallow. You can check out the code here: https://github.com/Widdershin/butterdb. I have grown a bit as a programmer since then, but I appreciate any feedback you might have.
I actually used this in production against my own recommendation to run the matching for /r/longboarding's Secret Santa. All of our data came from Google Forms, so it just made sense.
Hit me up if you have any questions.
Hey folks, I'm the author of this library. I actually renamed it to 'butterdb' a while ago because some people found fuckitdb hard to swallow. You can check out the code here: https://github.com/Widdershin/butterdb . I have grown a bit as a programmer since then, but I appreciate any feedback you might have. I actually used this in production against my own recommendation to run the matching for /r/longboarding's Sec…
This is a good library for interacting with Google spreadsheets, I've written an app with it: https://github.com/burnash/gspread
Earlier quoted context omitted.
It would have been more inappropriate. Which could be the goal, I don't know. But more seriously, it's legally risky to have anything to do with code licensed under WTFPL because it does not actually specify that you can do anything with the code without possible legal reprisals, from which no protection is offered. Probably safe to point and laugh at it, though.
Although the WTFPL website ( http://www.wtfpl.net/faq/ ) does note somewhat ominously that it hasn't been tested in courts, it seems legitimate enough to me. Is there any evidence outside of its lack of history in court that would indicate it isn't suitable for production use? EDIT: gnu.org also says "We do not recommend this license" ,pointing to the Apache license as providing better protection against 'patent trea…
This is a good library for interacting with Google spreadsheets, I've written an app with it: https://github.com/burnash/gspread