Earlier quoted context omitted.
Benefit? When my friendly junior developers add a variable where it isn’t supposed to go the system yells at them. This is much preferable to me yelling at them, or production getting broken. Typescript may be a little bit slower if you never make any mistakes ever , and can keep the full state of your program in your mind at a given time. Nobody makes no mistakes.
If you don't require at least 2 approvals from medior/senior developers for your junior's PRs you're doing it wrong. TypeScript is not a "little bit" slower, I've seen it take over 3 times more time (and frustrations, even for an experienced TS guru) to get simple things done. TypeScript is a colossal waste of time that many sheep gladly embrace because they feel they're expected to. Nobody dares to ask "but why?" wh…
Re: State of JavaScript 2019
#371I am reading your comments with interest. I do not find myself losing time using Typescript, quite the opposite, typing is in code documentation. And I find it much easier to read than untyped code. You say that TS dev focus more on code, maybe it is because they like to focus more on code that they use TS. I do agree you can waste time searching how to type a complicated piece of code. Meanwhile it is worth typing that piece of code if it is subject to change, or that the usage of it is not easy to understand.