> 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 th

> 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.