Not really. You'll notice a pattern in most tech bigcos where they move from dynamic lang X to a statically typed language that can multithread properly.
A few examples: Ruby on rails to java (twitter). Java & c++ (google). Java (linked in). Python/Node -> Java/Go (uber). Or they start doing silly things like make a new VM (facebook).
> That seems silly. There are far more Java devs out there than Go devs.
I wouldn't underestimate the level of hype-driven development that exists in this area. "Chasing the new shiny" seems like it could be a line item in a resume, these days, sometimes.
Wouldn't survivor bias explain who BigCo X can be found using whatever questionable choice they originally made, but not explain why lots of BigCos have changed their practices.
This might explain Facebook and PHP, but it doesn't explain the stuff mentioned in the previous comment.
Don't be obtuse, it's not because of multithreading.
They move to static typed because their team is 100+ developers none of which knows the entire code base - and static typing helps lower the bugs possible.
