When you start getting to a certain scale, developers are cheaper than your server costs in some cases. That is when something being performant is more worth it.
When you start getting to a certain scale, developers are cheaper than your server costs in some cases. That is when something being performant is more worth it.
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).
This might explain Facebook and PHP, but it doesn't explain the stuff mentioned in the previous comment.
Also, I would assume Uber probably has hiring problems in general at this point.
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.
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.
I don't think threading is a relevant factor for many of those decisions. Perf and static typing, sure.
Walmart also moved to node.js.
Hype was real.
I never missed static typing on large code bases but I had numerous bugs caused by python's implicit type conversions - string to iterable of characters ["h", "e", "l", "l", "o"], None to False, string "no" to True, 0 to False, "" to False, etc.
A lot of this mirrors C's infuriating implicit type conversions.