>> However, when I moved to my current role, working on JavaScript was not a choice, as all the apps I was going to work on, were written in TypeScript Classic

>> However, when I moved to my current role, working on JavaScript was not a choice, as all the apps I was going to work on, were written in TypeScript Classic stockholm syndrome. It sucks but I have to use it to survive so now I love it. >> Making impossible states impossible Well if they're already impossible, there is no need to make them impossible. >> exhaustive checks There is no such thing in coding. You can never exhaustively check all possible issues. >> Spotting bugs early How about learning to write good tests? >> Rich IDE support and ease of refactoring Yes, TS makes it much easier to write and refactor spaghetti code with low cohesion and tight coupling. If you have clean code with good separation of concerns, it makes no difference to the refactoring experience at all if you're using TS or JS. Why TS developers always talk about refactorings? If you need to 'refactor' your code, it means you designed it wrong. Perhaps TypeScript encourages over-engineering which necessitates constant refactoring?