Cooklang – Managing Recipes in Git • Hacker News Board

Re: Cooklang – Managing Recipes in Git

#11

Post by picardythird » Mon, Mar 07, 2022, 3:12 AM UTC

newman314 wrote: post #6

peterfield wrote: post #4

I followed the recipe to the letter. I've flipped the steak a few times already and I'm still waiting for it to brown. The butter is not melted either. Not really surprising considering the pan is cold :( Even with a hot pan, I would have put the butter first, not after the steak.

You want to wait until the skillet is ripping hot before you drop the steak in. I usually wait until I'm ready to finish cooking before dropping the butter in. Butter burns quickly so you do not want the butter in there for a long period of time.

One thing I heard and have had great results with is pre-melting the butter and skimming off the solids

Re: Cooklang – Managing Recipes in Git

#12

Post by bribri » Mon, Mar 07, 2022, 3:14 AM UTC

picardythird wrote: post #11

newman314 wrote: post #6

Earlier quoted context omitted.

You want to wait until the skillet is ripping hot before you drop the steak in. I usually wait until I'm ready to finish cooking before dropping the butter in. Butter burns quickly so you do not want the butter in there for a long period of time.

One thing I heard and have had great results with is pre-melting the butter and skimming off the solids

I’ve been using ghee which works really well for high heat searing

Re: Cooklang – Managing Recipes in Git

#13

Post by chrysoprace » Mon, Mar 07, 2022, 3:37 AM UTC

I looked into making a recipe site for my girlfriend from scratch a few years ago (I'm well aware I could've used an off-the-shelf Wordpress plugin or similar, but I wanted to learn) and I was surprised to find that there's no real consensus on recipe formats. I dream of a universal format that would allow you to take any recipe and convert between unit systems, and change the portion sizes at will. I suspect one of the reasons for the lack of adoption of such a standard is that copyright law (at least in Australia), makes this impractical. Cooklang looks interesting, but it has the same problem as a physical lined cookbook - I have to rewrite the recipes myself instead of being able to simply copy and convert.

Re: Cooklang – Managing Recipes in Git

#14

Post by dcchambers » Mon, Mar 07, 2022, 4:20 AM UTC

This is my first time encountering Cooklang and the concept is really neat, but wow the language syntax is...interesting.

My first thought was how this would be useful for easily including recipe scaling up/down on a website, and it appears that Cooklang has support for that...(or it's still a WIP: https://cooklang.org/docs/roadmap/)

Re: Cooklang – Managing Recipes in Git

#15

Post by PradeetPatel » Mon, Mar 07, 2022, 4:31 AM UTC

Sorry if this comes off as a noob question, I'm not a technical person but came from a marketing background.

Generally what is the monetisation model for founders developing languages like Cooklang? Would they sell support for the language, or create an ecosystem around it?

Re: Cooklang – Managing Recipes in Git

#16

Post by neetle » Mon, Mar 07, 2022, 4:34 AM UTC

PradeetPatel wrote: post #15

Sorry if this comes off as a noob question, I'm not a technical person but came from a marketing background. Generally what is the monetisation model for founders developing languages like Cooklang? Would they sell support for the language, or create an ecosystem around it?

Not everything needs a financial incentive

Re: Cooklang – Managing Recipes in Git

#17

Post by bribri » Mon, Mar 07, 2022, 4:45 AM UTC

PradeetPatel wrote: post #15

Sorry if this comes off as a noob question, I'm not a technical person but came from a marketing background. Generally what is the monetisation model for founders developing languages like Cooklang? Would they sell support for the language, or create an ecosystem around it?

The author does offer a paid app which lets you build shopping lists and view recipes, so there are some options for monetization.

Re: Cooklang – Managing Recipes in Git

#18

Post by peterfield » Mon, Mar 07, 2022, 5:08 AM UTC

picardythird wrote: post #11

newman314 wrote: post #6

Earlier quoted context omitted.

You want to wait until the skillet is ripping hot before you drop the steak in. I usually wait until I'm ready to finish cooking before dropping the butter in. Butter burns quickly so you do not want the butter in there for a long period of time.

One thing I heard and have had great results with is pre-melting the butter and skimming off the solids

Yep. It also boils out the 15-20% water content of butter to make it closer to 100% fat. Once you remove these (water + proteins and other impurities) the smoke point is much higher and it is much healthier for hot cooking. It is called "ghee" when done at medium high temp, which gives it a slightly darker colour and nuttier taste (Indian way I think), and just called "clarified butter" when done at low temp. Other advantage when done properly -> it does not go "off" anymore and does not need to be kept in the fridge, so you have this much easier/softer substance that you can spoon out of a jar.

You can even use it for deep frying - honestly the best fat for it.

Re: Cooklang – Managing Recipes in Git

#19

Post by nobodywasishere » Mon, Mar 07, 2022, 6:25 AM UTC

chrysoprace wrote: post #13

I looked into making a recipe site for my girlfriend from scratch a few years ago (I'm well aware I could've used an off-the-shelf Wordpress plugin or similar, but I wanted to learn) and I was surprised to find that there's no real consensus on recipe formats. I dream of a universal format that would allow you to take any recipe and convert between unit systems, and change the portion sizes at will. I suspect one of…

There is a recipe schema[1] that the Nextcloud app Cookbook[2] uses for adding recipes just by pasting a URL. Not every website supports this though.

[1]: https://schema.org/Recipe [2]: https://github.com/nextcloud/cookbook/

Re: Cooklang – Managing Recipes in Git

#20

Post by yuroFlash » Mon, Mar 07, 2022, 7:01 AM UTC

neetle wrote: post #16

PradeetPatel wrote: post #15

Sorry if this comes off as a noob question, I'm not a technical person but came from a marketing background. Generally what is the monetisation model for founders developing languages like Cooklang? Would they sell support for the language, or create an ecosystem around it?

Not everything needs a financial incentive

Fireship: The Dark Side of Open Source / What really happened to Faker.js? https://youtu.be/R6S-b_k-ZKY