Peter Reeves
@peterreeves.bsky.social
Web developer in Sydney. Interested in Electric Unicycles (EUCs) and board games. (He/Him)
I don't remember that tagline, but it might've been referring to this article that got a lot of traction a long time ago?
idlewords.com/talks/websit...
idlewords.com/talks/websit...
The Website Obesity Crisis
idlewords.com
November 15, 2025 at 9:30 PM
I don't remember that tagline, but it might've been referring to this article that got a lot of traction a long time ago?
idlewords.com/talks/websit...
idlewords.com/talks/websit...
Plus SK pressures you to add validation to your remote functions to improve both security and type inference.
November 3, 2025 at 8:24 AM
Plus SK pressures you to add validation to your remote functions to improve both security and type inference.
I don't want put words into Rich's mouth, but SvelteKit's remote functions feel different from the "server functions" he describes in that talk. SK's remote functions are separated by module boundaries so you don't hit issues with scope, serialization, or source maps.
November 3, 2025 at 8:24 AM
I don't want put words into Rich's mouth, but SvelteKit's remote functions feel different from the "server functions" he describes in that talk. SK's remote functions are separated by module boundaries so you don't hit issues with scope, serialization, or source maps.
Perun is a national treasure. His deep analysis with a sprinkle of humour on top makes it surprisingly good to watch.
November 3, 2025 at 7:55 AM
Perun is a national treasure. His deep analysis with a sprinkle of humour on top makes it surprisingly good to watch.
Every time I go back to vanilla JS I forget how many small gaps Svelte elegantly fixes. Makes me appreciate it more and more every time.
October 28, 2025 at 2:28 AM
Every time I go back to vanilla JS I forget how many small gaps Svelte elegantly fixes. Makes me appreciate it more and more every time.
Ugh indeed. Hoping these things get stuck in legal issues and are never rolled out here.
October 28, 2025 at 2:25 AM
Ugh indeed. Hoping these things get stuck in legal issues and are never rolled out here.
Ahh, yeah fair enough.
There's been a few times where I've been tempted to roll my own thing with the whole `<picture>` and `<source>` dance. Maybe one day I'll find the energy to do it.
There's been a few times where I've been tempted to roll my own thing with the whole `<picture>` and `<source>` dance. Maybe one day I'll find the energy to do it.
October 26, 2025 at 1:49 PM
Ahh, yeah fair enough.
There's been a few times where I've been tempted to roll my own thing with the whole `<picture>` and `<source>` dance. Maybe one day I'll find the energy to do it.
There's been a few times where I've been tempted to roll my own thing with the whole `<picture>` and `<source>` dance. Maybe one day I'll find the energy to do it.
When you save "doesn't let you pass any config down", do you mean something like this?
October 26, 2025 at 1:29 PM
When you save "doesn't let you pass any config down", do you mean something like this?
Though I have since clicked the link that michcia provided and seen that the docs show almost exactly what I was doing. Looks like those docs have been updated since I last looked (12+ months ago). Neat!
October 26, 2025 at 1:26 PM
Though I have since clicked the link that michcia provided and seen that the docs show almost exactly what I was doing. Looks like those docs have been updated since I last looked (12+ months ago). Neat!
Likely yes. I just whipped that example up based on a previous project I did a long while ago, and I had complicated logic to search for specific images by filename, so me doing `Promise.all` in that example was just me trying to slim it down to a screenshot and not thinking it through😅
October 26, 2025 at 1:26 PM
Likely yes. I just whipped that example up based on a previous project I did a long while ago, and I had complicated logic to search for specific images by filename, so me doing `Promise.all` in that example was just me trying to slim it down to a screenshot and not thinking it through😅
I think you should be able to feed that `imgUrl` into `<enhanced:img>` and it should work? I can't remember, it's been a while since I've done a setup like this. Keep in mind this approach only works if you're pre-rendering the data at build time.
October 26, 2025 at 11:37 AM
I think you should be able to feed that `imgUrl` into `<enhanced:img>` and it should work? I can't remember, it's been a while since I've done a setup like this. Keep in mind this approach only works if you're pre-rendering the data at build time.
Here's how you can use the `import.meta.glob` to show a list of images. You'll need a `+page.server.ts` and a `+page.svelte`. I wouldn't necessarily blame the complexity of this on Svelte, it took me a few goes of reading the Vite documentation to work out how to do this 😂
October 26, 2025 at 11:34 AM
Here's how you can use the `import.meta.glob` to show a list of images. You'll need a `+page.server.ts` and a `+page.svelte`. I wouldn't necessarily blame the complexity of this on Svelte, it took me a few goes of reading the Vite documentation to work out how to do this 😂
And also thanks to all three of you Netlify people for answering my continuous questions 😅
October 17, 2025 at 11:36 AM
And also thanks to all three of you Netlify people for answering my continuous questions 😅
Lol I just found the page on Edge Functions and was about to respond.
It looks like they're always global? i.e. if I have DB replicas in Australia and Europe I can't limit the edge functions to run in only Australia or Europe?
Might be an ok tradeoff, maybe I need to do some experimenting.
It looks like they're always global? i.e. if I have DB replicas in Australia and Europe I can't limit the edge functions to run in only Australia or Europe?
Might be an ok tradeoff, maybe I need to do some experimenting.
October 17, 2025 at 11:28 AM
Lol I just found the page on Edge Functions and was about to respond.
It looks like they're always global? i.e. if I have DB replicas in Australia and Europe I can't limit the edge functions to run in only Australia or Europe?
Might be an ok tradeoff, maybe I need to do some experimenting.
It looks like they're always global? i.e. if I have DB replicas in Australia and Europe I can't limit the edge functions to run in only Australia or Europe?
Might be an ok tradeoff, maybe I need to do some experimenting.
Ahh, awesome. Thanks for explaining that Matt!
While I have you, am I also understanding the docs correctly in that the functions for a site can only exist in one region? E.g. I can't deploy a site which will run in `eu-central-1` or `ap-southeast-2`, choosing whichever is closer to the user?
While I have you, am I also understanding the docs correctly in that the functions for a site can only exist in one region? E.g. I can't deploy a site which will run in `eu-central-1` or `ap-southeast-2`, choosing whichever is closer to the user?
October 17, 2025 at 10:57 AM
Ahh, awesome. Thanks for explaining that Matt!
While I have you, am I also understanding the docs correctly in that the functions for a site can only exist in one region? E.g. I can't deploy a site which will run in `eu-central-1` or `ap-southeast-2`, choosing whichever is closer to the user?
While I have you, am I also understanding the docs correctly in that the functions for a site can only exist in one region? E.g. I can't deploy a site which will run in `eu-central-1` or `ap-southeast-2`, choosing whichever is closer to the user?
Fewer network trips before something is visible? That's probably the reason I'd put first.
October 17, 2025 at 7:17 AM
Fewer network trips before something is visible? That's probably the reason I'd put first.
Well, we're currently at ~30 domains. If business keeps doing well, I don't want to be in a situation where we suddenly have to move off Netlify because we got our 51st customer. We're also looking at doing licensees for smaller companies and individuals, so if that takes off we could have 500+
October 16, 2025 at 11:43 PM
Well, we're currently at ~30 domains. If business keeps doing well, I don't want to be in a situation where we suddenly have to move off Netlify because we got our 51st customer. We're also looking at doing licensees for smaller companies and individuals, so if that takes off we could have 500+
(I assume there's also an API for automatically adding new subdomains to a deployment? I had a peek at the docs but wasn't sure)
October 16, 2025 at 10:56 PM
(I assume there's also an API for automatically adding new subdomains to a deployment? I had a peek at the docs but wasn't sure)
Our company has one subdomain per customer, e.g.
`customer1.example.com`, `customer2.example.com`, etc.
Does this mean we'd be limited to ~50 customers if all are pointing to the same deployment? We have `docs.example.com` and other things so I don't think I can use `*.example.com` on Netlify.
`customer1.example.com`, `customer2.example.com`, etc.
Does this mean we'd be limited to ~50 customers if all are pointing to the same deployment? We have `docs.example.com` and other things so I don't think I can use `*.example.com` on Netlify.
October 16, 2025 at 10:53 PM
Our company has one subdomain per customer, e.g.
`customer1.example.com`, `customer2.example.com`, etc.
Does this mean we'd be limited to ~50 customers if all are pointing to the same deployment? We have `docs.example.com` and other things so I don't think I can use `*.example.com` on Netlify.
`customer1.example.com`, `customer2.example.com`, etc.
Does this mean we'd be limited to ~50 customers if all are pointing to the same deployment? We have `docs.example.com` and other things so I don't think I can use `*.example.com` on Netlify.
Currently using Netlify for our company homage. I've been considering if we should move more of our infra to Netlify, but this wording in the docs scares me: docs.netlify.com/manage/domai...
"We recommend assigning no more than 50 domain aliases to a site."
"We recommend assigning no more than 50 domain aliases to a site."
Add a domain alias
Ensure your site is available at all the expected domains by assigning multiple custom domains to your production site as domain aliases.
docs.netlify.com
October 16, 2025 at 10:53 PM
Currently using Netlify for our company homage. I've been considering if we should move more of our infra to Netlify, but this wording in the docs scares me: docs.netlify.com/manage/domai...
"We recommend assigning no more than 50 domain aliases to a site."
"We recommend assigning no more than 50 domain aliases to a site."
Neat, thanks. I'll look into it sometime. I assume that's already what the Rust crate I was using was wrapping, but I'll also try running it bare and see if I get the same results.
October 16, 2025 at 12:13 PM
Neat, thanks. I'll look into it sometime. I assume that's already what the Rust crate I was using was wrapping, but I'll also try running it bare and see if I get the same results.
Also worth mentioning that these were high res images with full 4:4:4 colour, since in this application we're expecting users to zoom in and inspect fine details.
October 16, 2025 at 12:08 PM
Also worth mentioning that these were high res images with full 4:4:4 colour, since in this application we're expecting users to zoom in and inspect fine details.
I believe that was also with all the threading/SIMD options turned on too, though I found that they only had a small improvement on encode speed.
Maybe if I have time this weekend I'll need to look into it again.
Maybe if I have time this weekend I'll need to look into it again.
October 16, 2025 at 12:05 PM
I believe that was also with all the threading/SIMD options turned on too, though I found that they only had a small improvement on encode speed.
Maybe if I have time this weekend I'll need to look into it again.
Maybe if I have time this weekend I'll need to look into it again.
Which AVIF encoder are you talking about specifically? I was using a Rust crate from about a year ago when I was last doing experiments. The JPEG encoding was so quick I didn't even bother to time it, where as AVIF was taking 30+ seconds per image if I recall correctly.
October 16, 2025 at 12:05 PM
Which AVIF encoder are you talking about specifically? I was using a Rust crate from about a year ago when I was last doing experiments. The JPEG encoding was so quick I didn't even bother to time it, where as AVIF was taking 30+ seconds per image if I recall correctly.