Am I the only one that prefers on - prem to cloud based infrastructure?

There is something about holding the bare metal in your hands, the sound of snapping in a dozen RAM modules, the smell of electronics coming out of their anti-static bags, the pain of rail lube getting in that fresh cut, the 'tink, tink, clunk' of your last spare cage nut falling down the rack onto the floor under your UPS. The feel of whatever that material they make the crash carts out of, while you push it down the aisle as it quietly goes thud thud thud as each wheel crosses the grooves between raised floor tiles. The heat pouring off the back of your rack while your body goes cold, realizing you have absolutely no idea which damn server is down because the UID light is covered with a waterfall of patch cables thicker thicker than vines in a jungle. But I'm a manager now and there's a bigger picture. The "there's never enough money in the budget to buy replacements or renew our maintenance" is so tiresome, I have embraced cloud infra. If leadership wants something, they pay for it, and there is no ability to 'not buy something' this month. Our SAAS stuff is always patched, or hardware will be as fast as leadership wants to pay for, and I don't have to have an engineer spend 90 minutes in the datacenter diagnosing the slightly dim amber light on a server. While platform/infra components still require hands on; being able to utilize serverless DBs and file system nodes, automated server deployments and tools, there is theoretically more time to tackle issues we've avoided looking at. I know that despite AWS & Microsoft's larger attack surface, they are going to have an overall better security stance. They will have a security team with width and depth that I will ever be able to afford. They have FAR more financial and reputational risk than my org does and generally commit resources to protect those. There are outages with both and they are LARGE with lots of media reporting, but when I look through some of our incidents when we were on prem, not only were they multiple days, it frequently involved paid incident calls with MS, an MSP signal flare, and always overtime. We have an outage now, the team doesn't have to stress, IT leadership just needs to have good communication and make sure that expectations are managed. Then, we have AAR, look at what we could have done to reduce the impact on us (almost always 'Leadership would need to pony up extra cash for greater redundancy and tooling), and we go about our day. In the mean time, I haven't taken a young engineer away from their spouse and child for two days straight, I didn't have to call anyone on vacation, and they don't burn out as quickly.