Quote:
Originally Posted by suzzer99
Can you elaborate on what you like?
Part of software engineering is the constant struggle to be as efficient as possible and provide as much value as possible. This is one of the reasons for the rise of devops, containers, etc. Have your devs building product and providing value for customers and not fighting with their tools. It's also why no one would ever use vanilla JS and manually deal with browser specifics.
TypeScript may require some extra work up front, but it removes an entire category of potentially time consuming and tough to debug errors. It also makes it way easier to understand APIs between functions, and internal code when you are coming into an existing project cold.
Imagine getting up to speed on two legacy JS codebases. One is in TS and one is in vanilla JS. Its gonna be way easier and you're gonna feel more confident making changes in the TS codebase. To extend this, imagine if test coverage is bad/ non existent in each.
Nothing is stopping you from not using TS and just hacking in vanilla JS at first and then adding TS later when you wanna make what you are doing more robust.