Hacker News Reader

Comment by pintxo | Hacker News Reader

This looks really fantastic.

Is anyone working on let's name it CookHub already? So essentially GitHub for receipts. The nerd in me wants to fork receipts and share my small adaptations to the community.

View on HN

That would be pretty cool. It would already work in github, but yeah a dedicated site would probably be better ;-). I'm afraid that the intersection of people interesting in cooking and people who know how source control works is likely pretty niche

The other problem I have with community cooking websites is that usually people always underestimate the cooking time and that's annoying as hell. Like people would say you need to cook onions for 10 minutes, while onions take close to 25 minutes to be cooked. On the French website marmiton, it was so ubiquitous that they have moderators come in and fix people's recipes.

Edit: see https://slate.com/human-interest/2012/05/how-to-cook-onions-...

Just another reason to allow easy forking ;-)

My issue with recipe timings is that even if you cook things for as long as it says, the overall time to cook the recipe is always very "optimistic". I assume the issue is some combination of marketing and the fact that the test cook was done by a professional chef who can dice 10 onions in a minute.

I imagine it’s done that way because people don’t necessarily know what to look for when cooking something. If some one doesn’t know how to cook steak, you can’t tell them “cook till medium rare”. So we start trying to come up with proxies.

I very much doubt that most recipe timings actually involve a timed test cook at all. They're just guesstimates.

Ingredient prep is intentionally left out of recipe timings. In theory, this lets everybody adapt the recipe timing to themselves, because only you know if you can chop two onions in three minutes or thirty seconds, but as with the Doomsday Device in Doctor Strangelove, it's worse than useless if nobody knows about it. "Why didn't you tell the world?"

> people would say you need to cook onions for 10 minutes, while onions take close to 25 minutes to be cooked

It's up to recipe author to define what they cook and how. If you think 25 min is better, fork it.

Or report the bug, which should probably have another name in this context.

That’s to caramelise onions. Cooking onions through takes a few minutes. Plenty of instances where you don’t want to caramelise onions.

Not really caramelise is more like 40 minutes. You do need at the very minimum 15 minutes to cook onions, 20 to 25 to “brown” them.

How do we specify "cook until translucent"?

I believe the term is usually "Sweat the onion"

The main problem for me (who am interested in cooking, as well as somewhat au fait with version control) is that at this point in my life, I could not for the life of me write down a recipe for almost anything that I cook, because it is all based on "enough" and "to taste", with cooking times being in the "well, you look at the ingredients and a cooking schedule effortlessly forms in your mind" (none, by the way, based on actual time), allowing me to do things like cooking things in the oven and three or four pots on the stove, and have everything ready at the same time, by staggering the start times.

And I literally cannot tell you how I do it, because at this point, I don't know. I do know how I got there, though. Cooking, lots of it, at various scales and in variously equipped kitchens.

Scale-wise, I have cooked for 1. And on the upper end, I have cooked for about 50.

https://based.cooking/

Fantastic idea! Another benefit I can think of having such a repository combined with this markup language is powerful semantic searches - filtering by sets of ingredients, and perhaps adding the ability to add tags to the recipes

certainly!

For that you would need to convert the recipes into some format, that is easy to query, like https://schema.org/Recipe or http://www.formatdata.com/recipeml/

At least the JSON conversion would be nice to have, then I could XSL-T it into RecipeML.

Yeah, the same here :-). We created a placeholder repo https://github.com/cooklang/recipes, but it still subject to workout structure and probably it makes sense to standardise units in some way.

There was a project a while ago that did this for tacos but it seems to have fallen by the wayside. (Or the catalog is complete)

https://github.com/sinker/tacofancy

I’m not sure you’d want to fork it like version control does. If someone makes a variation that is not a correction, you’d want to have that easily available on the main repo with a link back to the original.

https://www.cinc.kitchen/info/features lets you fork recipes. forkthekitchen.com (now dead) was another similar effort. So did diy.soylent.com (now dead as well).

I'm building something with that functionality currently at https://www.reciped.io/, I've turned the search off until it's actually ready to go, but you can see what a recipe would look like here: https://www.reciped.io/recipes/mushroom-and-onion-pizza/

Doesn't use recipe-lang though, just uses markdown.

FatHub: https://sr.ht/~martijnbraam/fathub.org/

Ingredients seem to form a tree but I think a DAG would be more appropriate.

Reply on news.ycombinator.com