Don’t get me wrong: your IDE using/intuiting TypeScript type definitions to help you code: great.
Coding in TypeScript: not so great.
(Which shall become apparent in five years’ time for all the reasons no one writes CoffeeScript today.)
For js I use FlowType because it allows you to put all of the type info into comment syntax and then the js itself is still valid js which will run in any js engine.
@aral the idea, as brendan eich kept saying, was to support “programming in the large”.
@aral interesting take. I always though CoffeeScript is dead because it wasn't widely adopted.
Typescript OTOH is widely adopted and supported by the majors framework.
If you only need to support modern browsers, you could just not use webpack and use ES6 modules.
@aral It is worrying where Deno is going with TS "as a path to programming in Rust." Because who needs Rust if you have Deno??
@aral maybe TS becomes part of the original JS like with many othet things 🤷🏻♂️.
What do you use now btw for helping our your types? I’ve seen some vanilla js code where they define types.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!