"Oh that thing that was an experiment and had billing caps turned on but we rushed in to production and now the whole business relies on that thing is in an outage and destroying customer trust we've barely earned yet"

I get the flip side but... 2nd order effects oof.

They are saying the announcement means more to them than just a headline that most will scroll past. Maybe you are seeing something I'm not.

I've been around Mormons, not a religion scholar, but it seems plausible to me the same "one upsmanship" mormons have with missions, large paternalistic families, avoiding "outsiders" (see: homeschooling), etc are common in other religious communities. Like maybe the protestant Christian one you are in?

But I don't think you meant it that way.

For anyone reading that wasn't around it was very much an irrational hysteria. The bigots latched on to it to spread fear and justify their dehumanization of gay people. There were people that tried to bring reason and science to the conversation but they were drowned out by the panic/bigotry.

There was no good reason for the AIDS phobia in the 80s.

I was a pretty poor CS student, in hindsight I'm surprised I got it to work.

AWS truly does let you focus on your business logic and abstracts a TON of undifferentiated work and well beyond the low hanging fruit of system updates and load balancing.

I guess put another way, providing a SaaS you need to have an SLA, those SLAs flow from SLO and SLIs and ultimately a risk profile of your hw and sw. The risk of a bad HBA alone probably means a day of downtime if you don't do things perfectly. AWS has bad HBAs, CPUs, memory, disks etc all day long every day and it's not even a blip for customers, never mind downtime. And if you don't model bad HBAs in your SLAs then your board is going to be pissed when that outage inevitably happens.

Now if you don't have SLAs and you like sysops, networkops, clusterops, dbops work then sure, YOLO.

I just don't see it. Given the nature of the services they offer it's just too risky not to use as much managed stuff with SLAs as possible. k8s alone is a very complicated control plane + a freaking database that is hard to keep happy if it's not completely static. In a prior life I went very deep on k8s, including self managing clusters and it's just too fragile, I literally had to contribute patches to etcd and I'm not a db engineer. I kept reading the post and seeing future failure point after future failure point.

The other aspect is there doesn't seem to be an honest assessment of the tradeoffs. It's all peaches and cream, no downsides, no tradeoffs, no risk assessment etc.