• 1 Post
  • 50 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle



  • You don’t have to. Absolutely not.

    But: As a potential user it provides some additional features your solution lacks. I can easily fork or clone your repo and change things if I need to. If I think it benefits the project I can easily offer these changes back to you, if I don’t I can still profit from future development on your side and incorporate my changes into it. I can very easily check what has changed between two versions without relying (trusting) your changelogs or performing a manual diff.

    But most importantly it is a matter of trust. Not so much trust in your intentions and the possibility of malicious code (Git won’t prevent that), but it obfuscates your code unnecessarily making it harder to continue if you at some point decide to stop maintaining it or even detect vulnerabilities as it is not easily accessible without knowing where to look for it.














  • We switched to Kitchen Owl and it works out okay. The recipe management is nice in theory, but doesn’t work well for most of our recipe sources (because of parsing issues most websites aren’t recognized and ingredient amounts are not parsed correctly for German recipes), but we usually just create an empty recipe with a link to the original. This isn’t perfect - in hindsight we should have stayed with Bring! because it just works better. We are hoping that the issues will be fixed sometime in the future although I am not sure what to expect…