cookwherever VS endoflife.date

Cook Wherever: https://cookwherever.com/

Cooking is hard. I want to cook more but I am usually too hungry to focus. I am building a site to help you with all stages of cooking, not just showing you ingredients and directions.

I have also realized the knowledge I have amassed for the “why” of cooking helps me cook without needing recipes mostly. I use ML/NLP to extract entities from ingredients and directions so contextual information can be provided to someone who is curious (ex. “you preheat your oven because …”)

I really like content creators, but following videos while cooking is a no-go for my attention span. I’m working on it, but directions will work as time stamps into a video for a recipe.

[1] https://github.com/cookwherever/cookwherever

TL;DR ive been consolidating my cooking knowledge in an open source recipe site https://github.com/cookwherever/cookwherever

Hey! I am excited to see people developing in this space since this is where my head is also at. Up until two years ago I was eating canned chili and soylent before I was shown the light with The Food Lab and Salt, Fat, Acid and Heat. Ever since I have been trying to share my knowledge on cooking with others with varying levels of success.

What has become clear to me is that there is no one size fits all approach to teaching cooking since it is usually a very cultural experience for most people (as many in the comments have pointed out). That said, SFAH makes the argument that most cuisines are much closer than people think when you consider the functional properties of the ingredients that you are cooking. Pizza is just pasta with yeast *Italian grandmothers slowly turn their heads towards this atrocity*

All of this to say, I believe recipes are critical to jump start the creative process of cooking. When any type of possible failure on the path to completion is experienced (ex. missing ingredient, burnt cookies, etc.) there MUST be some way of recovering or at the very least understanding how that happened.

I have been slowing taking notes on all the cooking knowledge I have come across and have been putting it along side the recipes that inspire me. Forcing learning on someone in the kitchen, who is already probably pretty hungry if cooking is seen as a chore, is not productive. Sharing the joy you get from the art that is cooking is IMPERATIVE for any type of educational resource.

If you are interested in my progress, or want to contribute go check it out! https://github.com/cookwherever/cookwherever

completely unrelated to your post, but just wanted to say thanks for your work on the rebooting of nyt’s ingredient parser. I use it in my project here: https://github.com/cookwherever/cookwherever (site is currently down due to the server being physically moved from our house lol). If you are interested in talking more about how i’m using it I would love to share :)

> where you can see overlapped timelines when support ended

I tried to generate a visual timeline for a given page (https://github.com/endoflife-date/endoflife.date/pull/2859, has some screenshots), but it was limited to a single page (so you'd only see nokia devices at once for eg).

It turned out that it is too hard to generate clear charts with vague data. We often only know whether is device is supported or not (true/false, see comments about samsung below in this thread), and don't have clear release dates.

I'll get to it someday (PRs welcome), but it might not work for the usecase we want (picking phones) because data on mobiles is very vague.

repairability score -> sounds interesting, will file an issue and see. The hard part is that there's no clear identifiers for devices (SWID/CPE are just not good enough) for us to track this kind of data from elsewhere easily.

Here's the PR where it was added by a user, "Based on a Rails core team member's comment"...

A lot of the communications regarding End of Life for Support is done very effectively here: https://endoflife.date/

https://endoflife.date (not mine)

a little similar to endoflife.date if anyone has ever come across it for Software versions?

We do this at https://endoflife.date API, and it works quite well.

I've created the `db.json` with the [end of life](https://endoflife.date/) api.

Something I've recently worked on is building an SQLite database of all the dependencies my organisation uses, which makes it possible to write our own queries and reports. The tool is all Open Source (https://dmd.tanna.dev) and has a CLI as well as the SQLite data.

Ive used it to look for software that's out of date (via https://endoflife.date), to find vulnerablilities (via https://osv.dev) and get license information (via https://deps.dev)

It's been hugely useful for us understanding use of internal and external dependencies, and I wish I'd built it earlier in my career so I could've had it for other companies I've worked at!

This is neat: https://endoflife.date/

I'm looking for a 3rd party vendor that can do the mindlessly tedious work of maintaining a library of software support dates. Think hundreds of thousands/millions of versions of software in an enterprise with ridiculous tech debt. Something like endoflife.date but much more far encompassing.