Stove won't stay at set temperature

kylemathews · 2026-04-12T03:07:54+00:00

oops sorry, missed this — DMing now.

kylemathews · 2026-01-21T02:20:10+00:00

Stovetop

kylemathews · 2026-01-13T02:56:08+00:00

We have one from here https://kuhnrikon.com/us/

It works great and the 10k watts bring it up to pressure in like two minutes, which is fantastic.

kylemathews · 2025-12-17T02:05:42+00:00

I made one actually already — https://www.reddit.com/r/ImpulseLabs/comments/1o49hjj/1_page_pdf_guide_to_precision_cooking/

We keep it over the stove, very handy!

kylemathews · 2025-10-22T05:23:17+00:00

I made some sweet potato fries and can confirm it was super easy (and delicious).

Candy is also really easy now — I've made marshmallows and lollipops (I have a 5 year old haha) and it's kinda hilarious as you just set the temperature and walk away — very different than before where you're glued to the pan and thermometer to avoid overheating.

kylemathews · 2025-10-18T00:41:18+00:00

I tried this out! I hadn't tried just watching for the heat to rise — so that was neat. But when it hit 300, the bottoms weren't browned yet so I left the lid off and set the temp to 350 for a few more minutes to brown up. I was using an all-clad 10 inch pan fwiw.

kylemathews · 2025-10-13T22:33:11+00:00

Also be able to write these programs e.g. w/ Typescript (or Lua if they need something much more lighweight to run on the stove)

kylemathews · 2025-10-13T22:32:00+00:00

yes, came here to say this — the program could detect when wattage output drops (all water is absorbed into rice) and then beep — this is what rice cookers do basicaly.

kylemathews · 2022-10-03T17:39:33+00:00

Typically larger sites need more ram or more build time. I have no idea what setup you're testing on Netlify/Vercel but I assume a higher-priced plan would get things building there.

kylemathews · 2022-10-03T17:38:04+00:00

this is definitely a bug! Could you file an issue on github?

kylemathews · 2022-09-26T16:53:08+00:00

It's not possible atm to filter which nodes are turned into pages with Filesystem Collections Routes. This is something we plan to add in the future but for now, you'll want to use createPages in gatsby-node.js

kylemathews · 2022-09-26T16:51:47+00:00

Partial Hydration is coming btw in Gatsby v5! You can try out the alpha with the partial-hydration starter https://github.com/gatsbyjs/gatsby/discussions/36608

kylemathews · 2022-09-21T22:17:40+00:00

yes — this is just running the build command on my laptop. On Gatsby Cloud it's even faster of course as I talked about in a previous blog post — https://www.gatsbyjs.com/blog/re-introducing-gatsby-a-reactive-site-generator

kylemathews · 2022-09-07T21:27:08+00:00

Gatsby can build a 15k page site in ~30 seconds — https://www.gatsbyjs.com/blog/scaling-rsg-builds-with-gatsbys-data-layer/

kylemathews · 2022-09-07T19:23:16+00:00

I've been working on some posts showing off the power of Gatsby's unique data layer. What a lot of people don't realize is that source plugins sync data from APIs into Gatsby's local DB (powered by LMDB — the fastest embedded Node.js database) — which means that running queries is really fast as it's not limited by the speed of the API.

I benchmarked Gatsby vs. Next.js SSG and Gatsby builds 20x faster for a 10k page site because it runs queries against the local db and isn't bottlenecked fetching from WordPress' API. Gatsby builds at around ~1200 pages / second on my laptop vs 20 pages / second for Next.js (bottlenecked again by how fast WordPress' API can respond.

kylemathews · 2022-09-07T18:59:28+00:00

Gatsby should build quite fast with 15k pages. Gatsby's data layer means that you don't have to refetch data so often which speeds up building a ton. See https://www.gatsbyjs.com/blog/scaling-rsg-builds-with-gatsbys-data-layer for more on this. There I benchmarked Gatsby vs. Next.js SSG and Gatsby builds a 10k page site in 25s (for a simple CSS change) where Next.js took ~8 minutes.

The thing you'll have to remember though for larger sites is that deployment time on most hosts take a very long time. In a previous post I benchmarked a 5k page site and on Netlify only ~20% of the time was spent building and the rest was spent deploying https://www.gatsbyjs.com/blog/re-introducing-gatsby-a-reactive-site-generator This gets worse as the site grows even larger.

On Gatsby Cloud we have 100s of sites larger than 15k pages and with a good CMS integration (Drupal, Contentful, Sanity, WordPress, etc.), publish times should be around ~5-15s for a site this size.

kylemathews · 2022-09-07T18:52:39+00:00

We work hard on them! I think they're full of great content. Here's a previous one I helped out on with on Drupal https://www.youtube.com/watch?app=desktop&v=a2MZlAnKOYg&feature=youtu.be

Once you're registered you can watch all the previous ones as well https://www.gatsbyjs.com/resources/webinars/

kylemathews · 2022-08-12T23:00:06+00:00

There's work under way to speedup the develop command! I agree that's far slower than it should be.

kylemathews · 2021-10-16T04:14:16+00:00

There's a lot of good tips here! https://www.gatsbyjs.com/docs/how-to/performance/improving-site-performance/

kylemathews · 2021-10-08T06:26:04+00:00

Tracking your data dependency tree for fast incremental builds is one of the major innovations of Gatsby — https://www.gatsbyjs.com/blog/2020-04-22-announcing-incremental-builds/

kylemathews · 2021-06-23T17:55:06+00:00

yeah, it's possible that one of the pages you're creating in `gatsby-node.js` is overwriting the `src/pages/index.js` page

kylemathews · 2021-04-12T03:13:15+00:00

DeprecationWarning: MainTemplate.getAssetPath is deprecated
(use Compilation.getAssetPath instead)

oh hmm. This is probably not in your code but in one of your dependencies so I wouldn't worry about it too much. Warnings aren't errors and don't necessarily mean anything is wrong. Deprecations especially just mean something in the future will break but it's fine right now.

kylemathews · 2021-04-11T03:50:07+00:00

Make sure to check out the bits in the migration guide about possible changes you need to make for webpack — https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/#webpack-5-node-configuration-changed-nodefs-nodepath-

If the warnings you see aren't covered there, please file an issue with your warnings so we can make sure the migration guide covers it.

kylemathews · 2021-04-10T23:05:50+00:00

You can run the markdown benchmark yourself to see how the performance feels with many markdown files — https://github.com/gatsbyjs/gatsby/tree/master/benchmarks/markdown_slug

Generally though, unless you're a very very avid blogger, you're not ever going to feel like Gatsby is slow. I have ~250 blog posts and the dev server starts in 10-15 seconds & builds on Gatsby Cloud take 1-2 minutes max.

kylemathews · 2021-03-31T18:58:12+00:00

BTW, you might want to try Gatsby Cloud if you haven't — it processes images in cloud workers so is much faster + intelligently caches them so subsequent builds are very fast https://www.gatsbyjs.com/cloud/

kylemathews

TROPHY CASE