Meh large companies have large numbers of devs with varied opinions and power to apply those opinions. Lots of things we think of as shit now and have since dropped like a heavy coat has no doubt been implemented at one time by at least 1 of the companies you listed. It's whether they stand the test of time.

The number of man hours invested (wasted imo) into pointless layers of container stacks is mind blowing and I'm yet to see the return on investment for any of it in real world scenarios. The cynic in me sometimes thinks you get some new abstraction to beta and the set up your own con and get some time off work to talk about it, and having been a primary speaker at a conference gets your CV gravitas. Theres a con for every goddam library any Big Name releases before you can even properly evaluate it in a prod stack.

As as side point that doesn't entirely fit with my argument the most important lesson I took away from dev conferences when I still went to them is that devs wax lyrical about all kinds of things in public, but often the things they talk about are their pet projects or sidelined to some small part of the business that doesn't really affect the main workflow, yet because they work at a Big Name we attach importance to it.

All the companies you name have significant engineering manpower to dedicate whole teams to maintain all the tooling so that the devteams don't need to worry about maintaining their containers, VMs and whatnot.

I dare say that all that microservice stuff only works with 300+ employees if you keep everything containerized.

Where are these magically difficult to maintain containers? I regularly deploy stuff via containers and moving my github repo to a container to being deployed is very simple.