I saw cooklang but only after I made my app. It’s interesting but for me the main goal was to use existing recipes. I wanted to just take something I found online and be able to use it, not have to rewrite it. And I wanted it to handle multiple languages. When the first decent LLMs came up I did some testing and they were capable of transforming recipes into JSON so I build my app around that but the JSON had to very simple. I later managed to add couple extra features (like groups of ingredients) but it’s still way simpler than cooklang. Current LLMs could handle cooklang without issues but my app already does everything I need it to do so I’m not changing anything.
Nice! I thought about doing the same and then discovered https://cooklang.org/ - looks like it’s a similar approach that you describe
I saw cooklang but only after I made my app. It’s interesting but for me the main goal was to use existing recipes. I wanted to just take something I found online and be able to use it, not have to rewrite it. And I wanted it to handle multiple languages. When the first decent LLMs came up I did some testing and they were capable of transforming recipes into JSON so I build my app around that but the JSON had to very simple. I later managed to add couple extra features (like groups of ingredients) but it’s still way simpler than cooklang. Current LLMs could handle cooklang without issues but my app already does everything I need it to do so I’m not changing anything.
Ah very interesting! I found cooklang to be overkill for my needs as well but the fact that there’s an obsidian plugin resulted in me using it now.