Yes - and the 1/8 of a cow is needed to make milk to make butter. This might be possible if you were very selective about which eighth of a cow you procured, but you’d need some additional kit which the recipe doesn’t account for.
Some of the $0 items are the base "from scratch" items. You can click on an item to make it from scratch; doing so for eggs gives an egg-laying chicken (with an associated price), but doing that again gives the base level of "baby chicken." Not everything goes down that far (e.g. baking powder) but things like soil and seawater are of that ilk. See also: vanilla
Really interesting concept, but I think something is very wrong with whatever it is doing to (intentionally?) highjack browser histories/navigation on every page.
For example, if I just click "Refried beans" on the homepage, then click the recipe for "Refried beans" from the ingredients list on that page... it takes pressing Back on the browser FIVE times before I'm finally back at the homepage. And, interestingly, at no point during this process do I actually go back to the actually-previous page (where you land after clicking "refried beans" on the homepage) -- I just stay on the current page as the URL changes every time and then eventually make it all the way back to the homepage with nothing in-between.
> For example, if I just click "Refried beans" on the homepage, then click the recipe for "Refried beans" from the ingredients list on that page... it takes pressing Back on the browser FIVE times before I'm finally back at the homepage.
I must be getting old. There's no hijacking going on here, the page uses URL params, and probably JS to decode them.
I was expecting recipes to make something that's an ingredient of themselves, so that the recipe is truly recursive.
Now I'm trying to find out such examples of actually recursive recipe and I only find examples based on fermentation, which have a way to be bootstrapped but are then actually recursive: kombucha, kefir, vinegar, levain.
Fondant is much easier to make with some fondant as an ingredient. It acts as a seed to encourage the formation of the structure. I wonder if there are any mutually-recursive recipes.
They missed an opportunity with the eggs, which went egg -> egg laying chicken -> baby chicken but could clearly have then included baby chicken -> egg ...
Recursion doesn't imply infinite recursion; a recipe doesn't have to invoke itself to be a recursive recipe. Surely a recursive recipe is just a recipe that invokes a recipe.
This is completely normal; see Escoffier. E.g. for Cod Mornay, "Make a roux".
Escoffier's recipes were often just a single paragraph; you were supposed to know how the target tastes and looks.
Making sourdough is arguably infinitely recursive. You can break the recursion by looking up "Make a sourdough starter".
> a recipe doesn't have to invoke itself to be a recursive recipe
Er, no. That IS exactly what recursion means. It doesn't have to be infinite - there can be a halt condition - but if something doesn't call itself, it is not recursive.
These are not recursive recipes at all; they're just nested.
> Surely a recursive recipe is just a recipe that invokes a recipe.
No, a recursive recipe is one that (directly or indirectly) invokes _itself_. That's the whole point of recursion (literally, come back (=re) turning (=cur)).
Surely Wikipedia would mention such a unique property if it were true, but I can't find a mention of that an ingredient for kit kats is a (fractional) kit kat on https://en.wikipedia.org/wiki/Kit_Kat
A Kit-Kat bar consists of some external components, like wafers and chocolate. It's only the combination that turns them into a bar.
So you can bootstrap production by grinding the components and mixing them: it produces a Kit-Kat bar in a ground state. After that, you can produce more and more nominal-state bars.
This is actually something I feel lack in lot of recipes. They are often "too simple", as in they assume a lot of knowledge. Let's say you're making cinnamon buns. The recipe will basically just say mix these ingredients, knead, let it raise, roll, add stuff, bake.
But it lacks all the details. Like how do you work the best with different kind of yeast? How do you know if you got the right texture / amount of liquid? What about all the tricks and tips when working with this kind of baking stuff?
Old school cooking books are often better at this. There the cinnamon bun recipe would be "use the base bun dough from page X, but use only Y amount of ingredient Z". And then on the base recipe, all you need to know about doughs are covered.
Similarly, a recipe with meat will just say "cook until done", and then you need to know yourself how to best sear it, the temperature at which it is done etc.
Perhaps this is a place where LLMs can shine. It can fill in the perfect amount of knowledge for me if I'd ask it.
There has always been a distinction between (basic) cooking books that teach basic recipes and the accompanying cooking techniques on one hand and recipe books.
But there also was always the assumption, that people pick up very basic techniques starting as a child by helping in the kitchen, beeing shown by it and doing it themselves.
You might like Harold McGee's "On Food and Cooking" which is basically a popular science food chemistry "textbook" (it doesn't really go in the chemistry details but it usually gives you some pointers). It's got a chapter on dough iirc :) It's an excellent bathroom book because you can just open any page to find some quirky facts about foods.
In the recipe the third step of making yogurt calls for yogurt.
> 3. Stir in some yogurt (from the store or from a friend) and cover with a clean damp towel overnight.
It is kind of a missed opportunity to not include yogurt as the ingredients list for yogurt, and in the flow chart, to have a loop arrow from yogurt, pointing back into it self. “To make yogurt, you need milk and yogurt”
Readit News
- there's no recipe for the cow
- 1/8 of a cow is reported as $0.00
https://recursiverecipes.schollz.com/recipe/refried-beans?am...
For example, if I just click "Refried beans" on the homepage, then click the recipe for "Refried beans" from the ingredients list on that page... it takes pressing Back on the browser FIVE times before I'm finally back at the homepage. And, interestingly, at no point during this process do I actually go back to the actually-previous page (where you land after clicking "refried beans" on the homepage) -- I just stay on the current page as the URL changes every time and then eventually make it all the way back to the homepage with nothing in-between.
I must be getting old. There's no hijacking going on here, the page uses URL params, and probably JS to decode them.
Now I'm trying to find out such examples of actually recursive recipe and I only find examples based on fermentation, which have a way to be bootstrapped but are then actually recursive: kombucha, kefir, vinegar, levain.
Is there anything else?
This recursive dependency is not visualized sadly. Fun website nonetheless!
[0] https://youtu.be/2VrsmahNcfI?si=iDrWhkeAhrSQNMIF&t=549 Bon Appétit making gourmet Andes Mints
- 1 unit of vodka
- 2 units of water
- 3 units of Cocktail Recursive
(Where the salad the consituent is an alias for lettuce)
I can't imagine Russians mixing vodka with water, though.
Recursion doesn't imply infinite recursion; a recipe doesn't have to invoke itself to be a recursive recipe. Surely a recursive recipe is just a recipe that invokes a recipe.
This is completely normal; see Escoffier. E.g. for Cod Mornay, "Make a roux".
Escoffier's recipes were often just a single paragraph; you were supposed to know how the target tastes and looks.
Making sourdough is arguably infinitely recursive. You can break the recursion by looking up "Make a sourdough starter".
Er, no. That IS exactly what recursion means. It doesn't have to be infinite - there can be a halt condition - but if something doesn't call itself, it is not recursive.
These are not recursive recipes at all; they're just nested.
No, a recursive recipe is one that (directly or indirectly) invokes _itself_. That's the whole point of recursion (literally, come back (=re) turning (=cur)).
And don't call me Shirley.
Throw away the kernels, get more fruit.
I really want to believe this :(
A Kit-Kat bar consists of some external components, like wafers and chocolate. It's only the combination that turns them into a bar.
So you can bootstrap production by grinding the components and mixing them: it produces a Kit-Kat bar in a ground state. After that, you can produce more and more nominal-state bars.
Dead Comment
But it lacks all the details. Like how do you work the best with different kind of yeast? How do you know if you got the right texture / amount of liquid? What about all the tricks and tips when working with this kind of baking stuff?
Old school cooking books are often better at this. There the cinnamon bun recipe would be "use the base bun dough from page X, but use only Y amount of ingredient Z". And then on the base recipe, all you need to know about doughs are covered.
Similarly, a recipe with meat will just say "cook until done", and then you need to know yourself how to best sear it, the temperature at which it is done etc.
Perhaps this is a place where LLMs can shine. It can fill in the perfect amount of knowledge for me if I'd ask it.
But there also was always the assumption, that people pick up very basic techniques starting as a child by helping in the kitchen, beeing shown by it and doing it themselves.
I was thinking about this actually; are these actually recursive or just like self referential? But it's a recursive data type!
type Ingredient { ingredients: Ingredient[] }
> 3. Stir in some yogurt (from the store or from a friend) and cover with a clean damp towel overnight.
It is kind of a missed opportunity to not include yogurt as the ingredients list for yogurt, and in the flow chart, to have a loop arrow from yogurt, pointing back into it self. “To make yogurt, you need milk and yogurt”
EDIT: Looks like somebody already filed a feature request. https://github.com/schollz/recursive-recipes/issues/19