I don’t think so, and we build JS for enterprise and we were previously/are somewhat a mainly C# house. Typescript has some advantages that are appealing to pe

I don’t think so, and we build JS for enterprise and we were previously/are somewhat a mainly C# house. Typescript has some advantages that are appealing to people coming from Java/c#, and it integrates sort of well into a codebase that’s a mix of JS and typescript. So you don’t really lose that much from using it. We found it relatively burdensome compared to plain JS, simply put, it made us less productive. You fix some of JSs problems, mainly typesafety, but the trade off is that you’ll need to keep updated on both typescript and JS as well as getting a more complicated approach to prototypes and testing that isn’t as smooth (at least not for us, and that may be us not typescript but it’s still something you have to account for). If we were doing angular on the front end we might do typescript, but I honestly think we would’ve picked angularDart and flutter instead of typescript. I don’t think you go wrong either way though, typescript has just been unnecessary for us.