[runtime_terror]

For your first question:

- The workers platform is quite pleasant to work with compared to competitors. - Globally deploying edge workers which have access to their many services (D1, R2, DO, etc) - Having the ability to assemble globally distributed workers using bindings is dead simple - Their CI pipeline, while limited, is easy to setup and run and keeps improving - Their pricing is extremely competitive

For your second:

- That's my biggest conflict with using any service (Cloudflare, AWS, Azure, etc). Don't have a good answer with what to do about it considering for many projects I don't have the time/energy to fully self host everything.

[gonzalohm]

One thing is hosting, which obviously comes with centralizing risks but a different one is just deciding to add a layer of "protection" in front of every website so that as much traffic as possible goes through one single company.

[rs_rs_rs_rs_rs]

I love how you put protection in quotes like Cloudflare is some snake oil salesman and not a very good product.