With just a little bit of hyperbole:
The culture of Google is that you hire "the best" developers (say top 0.1%) and hamstring them with process and cumbersome tools so that you need 10x as many of them as another company would need and pay them 3x market rates, but it is OK because (1) at the scale they work at they can amortize the cost over a large user base and (2) they make monopoly products. Google's systems are highly scalable, I grant that, but they have the first mover disadvantage that their foundations are first-generation and not based on experience and still slowing them down... but the market can't discipline them.
Facebook on the other hand, cares about internal DX, sees it a problem when developers are stuck with cumbersome processes, and greases the skids. They benefit from huge scale and monopoly profits but Zuck is keeping more in his pocket than he would be if he did things like Google.
The problem with React is that mediocre developers can use it to build big things that are too big for them to handle. The problem with Kubernetes is that above-average developers can use it to build small things they can't handle. And the scalability of Kube is more than almost all of the industry needs. That is, a system like what Hazelcast was before it became an analytics play could support clusters of 30 or so big nodes (two racks) and there are probably just a few 100 systems in the worlds that really need to get bigger than that.
