Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have been using TypeScript at work since 2019. Personally I am not convinced that it is worth it, broadly for the reasons you note and also because TypeScript has in practice a soft dependency on Visual Studio, and in turn other MS services such as GitHub and Axure. Adopting TypeScript can often lead to de facto vendor lock-in.

There is a good argument for using types (and also a good argument for not doing so). If the argument for wins out, then types will be included in the native js spec and the need for TypeScript will disappear. If the argument against wins, then TypeScript will also disappear.

If TypeScript really floats your boat then by all means use it, but treat it for what it is- a hairy dependency that only a minority of developers love or need.



> TypeScript has in practice a soft dependency on Visual Studio

How do you figure? I've been fulltime typescript for almost 4 years now and never opened VS or Viscose once in my life.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: