I'm actually writing an argument against myself, because I'm usually closer to the "let's use the new shiny thing" camp. But that article is a nice reminder that the new shiny thing is not the only way to go and the "old, boring thing" is as capable if used right.

but Meta's versions are significantly different than the old, boring thing that you and I have access to. At my company, we are slowly rewriting our python services in golang because off the shelf golang incurs significantly less costs than off the shelf python on a per request basis.

Meta is actually contributing directly to upstream cpython. If you really wanted to, the internal fork is also open source: https://github.com/facebookincubator/cinder

>it seems silly to use “what FAANG companies are able to make their tools do” to inform decisions for smaller companies

Yes, and yet for many years now that's exactly the perpetual mistake that so many companies - both small ones and ones not in technology - would make because they assumed that if Google did it that way, it must automatically be the best.