[lou1306]

This answer is true, but also a bit depressing. It's like saying "we know this would be the right way, but we prefer the old ways. So we'll just keep shooting ourself in the foot with our C-looking code, with its for loops and its concurrency boilerplate".

(Just to be clear: "We" does not refer just to devs/engineers, companies may also be wary of using an alternate technology, even though it could bring benefits down the road)

[lostcolony]

Well, yes, but there is definitely a bit of dissonance in tech. Likely everywhere, but it's easy as a dev to see it here.

Every place wants to be the best. And yet, most places, when confronted with new technology, ask the same questions. "Who else is using it?", "How easy is it to hire for?", and if they're a bit sharper, "How much library/community support is there?" And they ask these without realizing that all of those questions will ensure they adhere to the mean. Positioning themselves that way prevents the risk of dropping below the mean due to technology choices, but it also prevents rising above it. But that's okay with most corporations, which are all about risk management, and who don't equate a tech win -> faster/better software -> better user experience -> a business win.