kmf

Hey, I’m on Cloudflare’s Developer Advocacy team — this is a top priority for the Pages team right now and big improvements to the build time are being actively worked on!

Wow, this looks so awesome! Really simple UI too — gonna have to give this a try. I was just struggling with some client-side image upload stuff last week, and I love the idea of doing the full service integration from client to backend as a product.

BTW - I’m part of the dev advocate team at Cloudflare, would you want to chat sometime about your experience with Images? Definitely would love to hear your perspective as a dev on what could be better!

The story around types in Workers should be leaps-and-bounds better than it was a few months ago (thanks to the work outlined in this blog post) - would love to hear your thoughts on this new work, and hope it helps!

kristian from pages team here - just DM-ed you, let's get this sorted!

hey, kristian from the workers team here - i wrote these docs, so this is good feedback :)

we don't have any plans to get rid of workers sites! but we do think that for most people deploying static sites, pages is a better fit than workers sites.

when we do talk about the future of pages versus workers sites, we're generally talking about making it easier to deploy serverless functions /with/ your pages sites - providing better tooling and DX around that is a super high priority for us.

the interplay between workers serverless functions and static asset serving via workers sites is still a really strong use case (and IMO a thing that workers is uniquely capable of doing) that we don't have any plans to shelf. again, i wrote the docs here so this is on me if it came across as "we're getting rid of workers sites" - i'll take a shot at improving these docs and helping clarify that next week!