Comment by satvikpendem
11 hours ago
A bunch of companies started a decade or two ago and became very successful using the dynamic language du jour back then, and now they're facing issues with said dynamism, so they introduce types to fix those issues, see Meta with Hack over PHP and Stripe with Sorbet over Ruby. The point is not for new users, it's for existing users to improve their development environments.
Are they _solving_ these issues of dynamism with typing? What other issues does it introduce?
Yes they are. Issues with typing on top is that it's not necessarily always robust enough, and not every company has the resources or premier language developer at the helm like Microsoft's TypeScript's Anders Hejlsberg.
whole lotta companies moving from ruby monoliths to ts distributed systems
Whole lotta companies regret doing that.
Take a working system and rewrite it as a series of separated network services that never quite implement the full original functionality in a new, trendy language just because.
It was a fad that new broom CTOs were keen on 5 years ago and I've seen a few companies killed by that decision.
There's so much unnecessary added complexity in running a distributed system of ts micro-services compared to a monolith. You need to be honest about that.