3 ms·
I think there is a fear TS will be deprecated in favour of a newer version of JS that supports what TS offers. I still remember back in ~2016 when a company I w
by danwee 4y ago
I think there is a fear TS will be deprecated in favour of a newer version of JS that supports what TS offers. I still remember back in ~2016 when a company I was working for was heavily invested in CoffeeScript. Granted, CoffeeScript was awesome and introduced some syntactic sugar (e.g., Class) that made the code easier to modularize and read. Nowadays JS brings almost all the nice things CoffeeScript was bringing to the table, so there is no need for CoffeeScript anymore. They are still working with CoffeeScript because refactoring the whole damn thing would cost a lot and they cannot justify it.
I think somthing similar may happen to TS.
- enduser 4y agoI had similar concerns early on with TS, but they have adhered closely enough to being "ES+types" and done so with such success that it would be hubris to implement a new ES standard type system. I know I can eject the types and go back to ES, but at this point I trust TS is going to be highly relevant for at least 5 years with a long tail.