[hzlatar]

I agree with points 1 and 2, but not with 3.

AWS isn't a developer tools company. It is ops tools company. In particular enterprise ops tools company. Their customers are IT managers and system administrators from large companies. That explains 1 and 2.

Famously, AWS is organized as huge bunch of two pizza teams. Essentially, it's a huge incubator for internal startups. That's how they manage to churn out new features so frequently and try out and discard unsuccessful products. Also, that is why their tools looks so damn inconsistent and why you never know what's working with what.

Regardless of money, they can't make the tools better without sacrificing something. And that is a space for competitors. Work on developer centric tools for small and medium sized companies.

[AtlasBarfed]

As I harped on in the AWS outage, when you combine this fact with the disruption of Stack Ranking/forced attrition, how does this lend itself to long term stability for something that is approaching utility-level importance for the economy?

Utility companies are staid and boring. That's a GOOD thing.

If AWS doesn't restructure, then what does it do? Re-re-reimplement all the internal bespoke systems that run AWS? Doesn't matter, their employees will turn over and the bitrot in those systems is about, what, four years?

Man I hope they are good at microservices!