> The 2x to 3x extra time that it will take to complete projects using TypeScript instead of JavaScript. I think you are doing something wrong. I switched ove

> The 2x to 3x extra time that it will take to complete projects using TypeScript instead of JavaScript. I think you are doing something wrong. I switched over to TypeScript for my personal projects 2 years ago and never experienced that. If anything there are a few rare cases where I run into problems up front due to type conflicts, but really each of these cases likely would have resulted in expected maintenance down the road. Problems down the road were pushed much forward. The increase of effort was tiny, and its possible to really say, but this could have been a cost savings over the costly concerns of debugging an embedded problem. > I have over 1 year of experience with TypeScript in multiple projects and earlier in my career I used ActionScript 3.0 (also typed ECMAScript) for over 3 years so unlike the people who make the decision to move to TypeScript, I know what I'm saying. That isn't very much experience for the claims you are making.