4 ms·
Nice, I have also created a language for recipe based on cook-lang (I didn't use cook-lang because I was not convinced by the syntax). The language is called re
by woile 2y ago
Nice, I have also created a language for recipe based on cook-lang (I didn't use cook-lang because I was not convinced by the syntax). The language is called recipe-lang[0] and it powers https://www.reciperium.com https://www.reciperium.com
Check it out, I've open sourced as well a syntax highlight for vscode, a cli for the terminal, a tutorial and a playground, and the wasm modules.
I use the language for more than food recipes, see:
https://www.reciperium.com/woile/garlic-tea-for-plants https://www.reciperium.com/woile/garlic-tea-for-plants
[0]: https://github.com/reciperium/recipe-lang https://github.com/reciperium/recipe-lang
- jdgoesmarching 2y agoWhat do you not like about cooklang? I’m in the early stages of building an app around it.
- woile 2y agoThe way ingredients and other things are described. I felt that explaining that a single word ingredient, requires @ only, but if you use multiple words, you have to use @ingredient with space{}, with the empty `{}` at the end can be too complicated to explain. I felt that for someone who is not familiar with these things, it can be confusing. In recipe-lang the explanation is IMO simpler: wrap the ingredient with `{}`, there are no ambiguities. {salt} or {ingredient with space}, it's quite clear where the ingredient starts and end. Once they learn that, everything else is a prefix of the curly braces, timer? t{}, link to another recipe? @{}, material? &{}. I'm considering for images something like i{} but I haven't had time to experiment with it.
- jdgoesmarching 2y agoInteresting, I’m nowhere near a place where I’m thinking about the implementation yet so maybe I’ll poke your version a bit!
- woile 2y agoawesome! let me know if you build something, I'd love to see more tooling around recipe-lang