I've migrated to Typescript and have been using it for about 2 years now. Maybe 1.5... TS is the best language I've used. It supports frontend and backend and

I've migrated to Typescript and have been using it for about 2 years now. Maybe 1.5... TS is the best language I've used. It supports frontend and backend and strict typing and it's scalable so I can refactor and know that my code still works. The one thing its not good at is ML where Python is better but that's mostly because Python has better library support (not language design). Here's the deal. When dealing with a large amount of code 80% of your dev time is spent maintaining code - NOT writing new code. You can save a lot of time now writing new code and not using strict typing. OR you can spend a little bit of time now, maintaining your types, and save a MASSIVE amount of time later. > - TypeScript compile time when changing files takes several minutes, making continuous compiling an excruciatingly slow process I have a HUGE typescript repo and using a Macbook Pro from 2015... With --incremental and --watch my build takes like 5 seconds. About 1 minute on the first build then about 5 seconds after that. If your build is taking a long time - you're doing something wrong. > The internal code and runtime TypeScript declarations must be manually kept in sync since the TypeScript Compiler isn’t helpful to generate the d.ts files What? How? That doesn't make any sense. You're doing something wrong here. If all the code is in typescript, you have no additional work to do. If it's in JS you just have to write your own .d.ts files manually. Honestly it seems like this team just needs to sit down and understand how their tools actually work. The one issue where Typescript DOES kind of suck is when dealing with webpack, typemaps, and types. Many older projects just don't publish types and if you rely on them, and they refuse to publish types, you're going to be in a bit of pain. You can write your own types though and we've been doing this internally and for some repos just forking them so it's a bit easier to work with them. They usually lag on publishing their types. If you want to avoid all this pain you can just use webpack for your build system and Typescript for your code. We use lerna to build a multi-module system with --hoist to avoid duplicate dependencies. https://github.com/burtonator/polar-bookshelf https://github.com/burtonator/polar-bookshelf ... is the project we're working on if you want to check it out. Our internal build system isn't fully published yet as we're in the process of reworking it but we're open source so you can take a look if you want.