Cloudflare is almost perfect

With a container pretty much all the common problems go out the window, especially those stupid cold start issues. The problem right now though is most other container-as-a-service products are either too expensive or too limited in functionality. Google Cloud Run is the closest to what I would want, but it is both too expensive to run and also locks you into the Google Cloud ecosystem which is both complex and expensive in every other way. … ## Workers HTTP imports ... Being able to do something similar to this with Cloudflare Workers would be amazing. However right now there is one big blocker, besides TypeScript support, and that is that there is no native support for HTTP imports. … - **S3 client**: `@aws-sdk/client-s3` sucks, both in terms of DX & package size. I wish Cloudflare would make their R2 worker API a general purpose package for anyone to use. The closest I have found that is good in the meantime is `@bradenmacdonald/s3-lite-client`. ## The dashboard sucks I'm sorry but I will put it blunt, ***it does suck.* ** It's slow, confusing UX where products are placed sparatically, fast page loads but data loads in slowly filling the page with loading spinners & often giant red banners at the bottom telling me about some internal error when trying to load the page. This isn't as much of an issue if you're using any kind of infrastructure-as-a-code system, but even then you would still need to use the dashboard to view analytics, billing, etc, and on that scenario it would be helpful if the dashboard was a bit more user friendly. … ## Sharable API key permissions This is a small one, but I think it would be really helpful for a niche number of developers and blog writers. In short, I wish that when you were creating a new API token in the Cloudflare dashboard that it would give you the option to copy a code, likely a hash of some kind, that you could then share around to paste in the exact permissions needed for something.