Comment by esseph
4 hours ago
I am paying $0 for this worker for years now.
(Actually multiple, one for each domain)
Actually if you even search "static sites" now it just takes you to Workers & Pages in the dashboard.
Docs:
https://developers.cloudflare.com/workers/
Free plan limits:
https://developers.cloudflare.com/workers/platform/limits/#a...
you don't explain the advantage of workers over pages for a static site
I think they've been merged, is my point. It's managed through the same interface now.
On the Pages docs website there is even a header that encourages you to use workers (though I don't think you're given a choice at this point), like pages in general are being deprecated.
---
Are you sure you want to use Pages?
Workers supports most Pages use cases and offers a broader feature set. It is Cloudflare's primary platform for building applications. Start new projects with Workers.
---
https://news.ycombinator.com/item?id=46037452
"We are not sunsetting Pages. We are taking all the Pages-specific features and turning them into general Workers features -- which we should have done in the first place. At some point -- when we can do it with zero chance of breakage -- we will auto-migrate all Pages projects to this new implementation, essentially merging the platforms. We're not ready to auto-migrate yet, but if you're willing to do a little work you can manually migrate most Pages projects to Workers today. If you'd rather not, that's fine, you can keep using Pages and wait for the auto-migration later."
"Now that Workers supports both serving static assets and server-side rendering, you should start with Workers. Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers. We aim to make Workers the best platform for building full-stack apps, building upon your feedback of what went well with Pages and what we could improve."