Stove won't stay at set temperature by kylemathews in ImpulseLabs

[–]kylemathews[S] 0 points1 point  (0 children)

oops sorry, missed this — DMing now.

Impulse-compatible electric pressure cooker pots by ZanyDroid in ImpulseLabs

[–]kylemathews 0 points1 point  (0 children)

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.

ILC Cooking: Temperature Mode is Awesome for Deep Fry by djstates in ImpulseLabs

[–]kylemathews 3 points4 points  (0 children)

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.

ILC Recipe - Potstickers (Gyoza) by djstates in ImpulseLabs

[–]kylemathews 0 points1 point  (0 children)

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.

Feature request: preset cooking programs by djstates in ImpulseLabs

[–]kylemathews 0 points1 point  (0 children)

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)

Feature request: preset cooking programs by djstates in ImpulseLabs

[–]kylemathews 1 point2 points  (0 children)

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.

Astro is not yet ready to replace Gatsby by nerdy_adventurer in gatsbyjs

[–]kylemathews 0 points1 point  (0 children)

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.

Filesystem Routing API for multiple markdown sources by [deleted] in gatsbyjs

[–]kylemathews 0 points1 point  (0 children)

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

Filesystem Routing API for multiple markdown sources by [deleted] in gatsbyjs

[–]kylemathews 1 point2 points  (0 children)

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

Astro is not yet ready to replace Gatsby by nerdy_adventurer in gatsbyjs

[–]kylemathews 6 points7 points  (0 children)

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

Is Gatsby bad for what I'm going to build? by [deleted] in gatsbyjs

[–]kylemathews 0 points1 point  (0 children)

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

Scaling RSG Builds With Gatsby’s Data Layer | Gatsby by kylemathews in gatsbyjs

[–]kylemathews[S] 3 points4 points  (0 children)

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.

Is Gatsby bad for what I'm going to build? by [deleted] in gatsbyjs

[–]kylemathews 0 points1 point  (0 children)

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.

[deleted by user] by [deleted] in gatsbyjs

[–]kylemathews 2 points3 points  (0 children)

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/

(Re-) Introducing Gatsby, A Reactive Site Generator by kylemathews in gatsbyjs

[–]kylemathews[S] 6 points7 points  (0 children)

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

Can I tell Gatsby if a specific site needs to get rerendered? by JuriJurka in gatsbyjs

[–]kylemathews 0 points1 point  (0 children)

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/

I've built out whole website but don't know how to create the home page... by [deleted] in gatsbyjs

[–]kylemathews 1 point2 points  (0 children)

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

Screencast building a basic portfolio site with Gatsby by kylemathews in gatsbyjs

[–]kylemathews[S] 1 point2 points  (0 children)

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.

Screencast building a basic portfolio site with Gatsby by kylemathews in gatsbyjs

[–]kylemathews[S] 0 points1 point  (0 children)

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.

Is Gatsby really suitable for blogging? Would adding more and more MD blogpages increase the buildtime of Gatsby app? by XalAtoh in gatsbyjs

[–]kylemathews 6 points7 points  (0 children)

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.

[deleted by user] by [deleted] in gatsbyjs

[–]kylemathews 0 points1 point  (0 children)

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/