Why? I don't see much unreasonable here.

Make infrastructure changes faster? Why not.

Make it easier to create ephemeral resources? Why not.

Make scaling completely automatic? Would be nice. Though here I'd of course like to have some knobs to control the automatic scaling, else it could easily run out of reasonable budget.

My only disagreement is client library vs declarative configuration. I'd prefer the latter, but using some better language than YAML; maybe, say, Dhall.

And yes, it's now a common wisdom that the cloud is the new mainframe; e.g. [1]. Well, okay; if this is what is required to run services at scale without breaking the bank, so be it. If deploying to millions of ZX-81 Spectrums happened to give 3x reduction in opex, the industry would adapt to that, too.

[1]: https://news.ycombinator.com/item?id=26857859

Yeah, I just love his breathless dismissal of the incumbents (Guess I'm a neo-luddite!)

In fact I think a lot of this optimism is in dire need of a couple of baseball-bat hits to the kneecaps.

> But things are rarely built to optimize for developer productivity.

Well, these a-holes abandoned Rails in favor of serverless-react-lambda-script. They made their bed, now they must lie in it.