For a lot of projects, TS is simply overkill (like a lot of stuff these days - looking at you, React). Often, we should simply embrace JS for what it is, and how it works. Dynamic typing can be extremely useful, as can features like implicit type coercion - if you understand them and how to use them. A lot of developers simply use TS as a crutch when coming from a strictly typed language, to avoid having to learn how JS does things. This is a mistake
That is not the case when you use typescript. You can use dynamic types when needed but dynamic type is so much prone to errors when working with team.
Also note that typescript does not change anything it just add layer of types on top of javascript so developer can get better experience programming.
I know what TS is, what it is used for, and how it works - I've used it, and can see why it can make sense in some projects. I'm just saying it isn't a good fit for some projects and it just adds unnecessary fuss and overhead.
It's also debatable whether having a layer of types on top of JS gives a better experience to the developer. Some developers (myself included) prefer dynamically typed languages and dislike the extra formality of working with typed code.
At the end it is personal preference. But if you are working on team than person preference does not matter that much and also type safety is must in some situations where you have to manage lots of things.
Every team that I've worked on uses typescript for better development experience across the board.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Horses for courses.
For a lot of projects, TS is simply overkill (like a lot of stuff these days - looking at you, React). Often, we should simply embrace JS for what it is, and how it works. Dynamic typing can be extremely useful, as can features like implicit type coercion - if you understand them and how to use them. A lot of developers simply use TS as a crutch when coming from a strictly typed language, to avoid having to learn how JS does things. This is a mistake
That is not the case when you use typescript. You can use dynamic types when needed but dynamic type is so much prone to errors when working with team.
Also note that typescript does not change anything it just add layer of types on top of javascript so developer can get better experience programming.
I know what TS is, what it is used for, and how it works - I've used it, and can see why it can make sense in some projects. I'm just saying it isn't a good fit for some projects and it just adds unnecessary fuss and overhead.
It's also debatable whether having a layer of types on top of JS gives a better experience to the developer. Some developers (myself included) prefer dynamically typed languages and dislike the extra formality of working with typed code.
At the end it is personal preference. But if you are working on team than person preference does not matter that much and also type safety is must in some situations where you have to manage lots of things.
Every team that I've worked on uses typescript for better development experience across the board.