Wow, so many misleadings in your comment. 🤫
Other guys will point them out. I just want to point out the biggest that you claim it hurts the development time.
Do you know that most of the IDEs rely on the typescript to build the autocomplete (based on the type definitions provided along with the libraries? Those type definitions are written using type script) that helps you accelerate your coding speed. Imagine you have to write a SW in notepad 🗒, or even worst, browse some source code in notepad. Well, jsdoc may help but it may deviate from the real implementation. Not cool.
Typescript can be JavaScript but JavaScript cannot be typescript. Who is superset now? 😎
From my own experience, it is much more difficult to maintain a software written in JavaScript than the one written in typescript. Some of my teammates tend to use JavaScript in a typescript project led to unmanageable source code which caused a lot of time to read and debug and enhance.
I bet that you didn’t have enough time working with typescript to have a good experience to leave a more fair comment than that. Hope you will give you another chance to be IN to the typescript. (Actually I don’t care since without you it is still good 😌)
Tech Lead/Team Lead. Senior WebDev.
Intermediate Grade on Computer Systems-
High Grade on Web Application Development-
MBA (+Marketing+HHRR).
Studied a bit of law, economics and design
Location
Spain
Education
Higher Level Education Certificate on Web Application Development
I just copied some argues that I've found on internet, applied some typical concerns on top of that and edited the output having a reasonable argument.
None of what I said is wrong, it just depends on many different factors such project structure, architecture, design and so on.
I use TS too, not a hater or something similar, but when you ask people for further/deep explanation they usually skip it, but when you type something that they feel incorrect or counters it's believes, they argue properly.
It was some kinda like an experiment with @akashshyam and we (as you can see) ended up with some good and structured comments from the engineering point of view, which is nice.
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.
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?
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.
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.
Wow, so many misleadings in your comment. 🤫
Other guys will point them out. I just want to point out the biggest that you claim it hurts the development time.
Do you know that most of the IDEs rely on the typescript to build the autocomplete (based on the type definitions provided along with the libraries? Those type definitions are written using type script) that helps you accelerate your coding speed. Imagine you have to write a SW in notepad 🗒, or even worst, browse some source code in notepad. Well, jsdoc may help but it may deviate from the real implementation. Not cool.
Typescript can be JavaScript but JavaScript cannot be typescript. Who is superset now? 😎
From my own experience, it is much more difficult to maintain a software written in JavaScript than the one written in typescript. Some of my teammates tend to use JavaScript in a typescript project led to unmanageable source code which caused a lot of time to read and debug and enhance.
I bet that you didn’t have enough time working with typescript to have a good experience to leave a more fair comment than that. Hope you will give you another chance to be IN to the typescript. (Actually I don’t care since without you it is still good 😌)
I just copied some argues that I've found on internet, applied some typical concerns on top of that and edited the output having a reasonable argument.
None of what I said is wrong, it just depends on many different factors such project structure, architecture, design and so on.
I use TS too, not a hater or something similar, but when you ask people for further/deep explanation they usually skip it, but when you type something that they feel incorrect or counters it's believes, they argue properly.
It was some kinda like an experiment with @akashshyam and we (as you can see) ended up with some good and structured comments from the engineering point of view, which is nice.
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.
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?
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.
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.
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.