Why github? You couldn’t just use pastebin? It’s a recipe! How much collaboration are you expecting to happen? Are you expecting people to file issues about your chili sauce?
I sure hope someone would fork it and iterate on the recipe, that's why version control exists. So you can have, you know, versions. Recipes are like software, except food pops out. Change the recipe, change the food. Change the recipe a little, change the food a little. Why wouldn't you want to post it to Github?
I'm not opposed to the idea, it just seems like a stretch of what github is made for. What did they select as the programming language for the repo? Junior devs struggle with git concepts, how will this catch on for mainstream recipe users?
Recipes are nothing like software. Software can return expected results for everyone who uses it. But everyone can tell you a story of a recipe not turning out right. The hardware for compiling a recipe is way too imprecise for the micro adjustments a version control system would be useful for. Compiling a recipe is all about reading and understanding what the author is intending and then adjusting for your own equipment and tastes.
It's also just a cheap post. What, now we can upload otherwise unnoteworthy content to github, and suddenly we're on the front page of HN?
> The hardware for compiling a recipe is way too imprecise for the micro adjustments a version control system would be useful for.
Not a bad point, I didn't think about it like that. However, I think this would be more useful to the people who are competent enough to implement nuanced recipes. Small changes in the recipe can lead to large changes in the food, much larger than the error between competent cooks. What if you have different tastes than the original recipe, and I like your taste? I'd wanna know about your changes, especially if I had the skills to implement them and I had a passion for cooking.
Plus, Generations have already been iterating and verbally passing down recipes for thousands of years. Most of that history is gone, and all we have is a thin slice which is what we know today. You only stand to gain by using version control for recipes.
But sure, Github probably won't explode as the go-to recipe database, because the intersection of git users and competent cooks is small compared the amount of cooks.
> It's also just a cheap post. What, now we can upload otherwise unnoteworthy content to github, and suddenly we're on the front page of HN?
This is not too important to me. Hey, we're all here talking about the post, so maybe it is noteworthy.
So it’s noteworthy and interesting, but here I am getting crushed with flags and downvotes. github can do no wrong, all within its walls are sacred, how dare he speak against our holy temple
Wouldn't that be great? If you think about it, it's surprising how GitHub's potential as a platform has been solely used for code up until now, taking into account that pretty much anything that can be represented as text may benefit from its "social coding" features.
There is much more to managing legal documents than simply tracking content changes. GitHub is not an effective tool for this, read some of the criticisms in the thread. There are better market offerings for lawyers that make signing, printing, and securing documents much easier.
I flagged the original submission because I honestly thought it was spam or a joke or something. Perhaps it’s a vindictive flag in return.
But yeah, there’s not much else to say about a recipe on GitHub aside from the fact that it is on GitHub. Am I the only one that finds it strange? Am I taking crazy pills?
FWIW, I downvoted the initial comment because it did not read as a honest inquiry, but more like "you're wrong, and I'm gonna ask a few dishonest questions to repeat how wrong you are".
