I've worked with both. And I have to say: It depends. Mostly I feel like typescript slows me down A LOT.
In my opinion, the better your code style, guidelines, linting, infrastructure, error reporting and tests - the less you need typescript.
I worked in a team that had about 150 micro-apps and services, it was maintained by roughly 15 devs. Each microservice had it's very small scope and it was very very easy to work with it. Everything was very predictable, which made it easy to work without having types.
I mean, I would be willing to work in company that does not uses typescript.
But a company that goes to irrational length of rewriting dependencies because they use typescript? A company that assumes that seniors don't make simple mistakes? Those are warning flags.
"We have problems, let’s introduce some code style guidelines, linting, error reporting and most importantly tests!"
"Nah, let's just switch to Typescript, it will solve all those problems. At least partially."
I mean, look at the number of tests needed to replace a few lines of types. You have to check the behavior of your functions for all kinds of invalid inputs. With typescript you still need tests but less of them. And also you can get rid of a lot of input validation in your production code.
No I didn’t. The statement was that Typescript solves the listed issues, which is obviously not true. There may be of course discussion whether TS _helps_ to solve such issues but you won’t be able to convince me that TS _solves_ e.g. lack of testing.
