DEV Community

Discussion on: To Typescript Or Not To?

 
maixuanhan profile image
Han Mai • Edited

What is the point to repeat the opinions commented by other guys? I don't think writing a long comment called a "deep explanation". In fact most of the points in your original comment are subjective and lack of the statistical evidence. And I think you've probably also known that because that kind of comment can be posted as an article itself but it would be low quality since lacking of foundation and yet it was just a comment.

BTW using TS is good, but always using it is a lack of analysis of what you really need. It help with different things but there's no warranty that by simply using TS you project will be better structured, more maintainable and so on, it will depend mostly on the implementation.

Since we are comparing b/w JS and TS, I have to say that using JS costs us extra effort to create a well structured project because it is dynamic. In contrast, TS with its rich support on type things will cost us less.

Knowing the bad parts of TS as well as the good ones can help us all to end up doing a better job, don't you think?

Till now, I find that only the learning curve is the disadvantage of TS (comparing to JS). Some young folks may read your comment and directly say NO to the TS, that why I have to speak out the "misleading" word which is nothing personal. Again, it is my subjective opinion but then those folks will notice the controversial and will look into the topic carefully and finally make a better decision to continue to be IN with TS or not.