Still convinced TypeScript has added 10x more complexity and struggle to catch bugs that could be caught by CI. 🤷 I guess there's the fancy intellisense stuff too but I don't use it so 🤷🤷
@mauve i honestly find types most useful for doc linking, so i can describe and discover the intended shape of stuff. clojure does this with specs (which i like!) and i kinda think js / python just imitate rust for a fraction of the benefits. i’ve used types with python and it was cool for doc linking but primarily annoying
@mauve at least with specs your type defs write their own tests
@mauve Typescript always feels like there was a whole class of person that could just ask for something and get it, and now there's five different ways of doing everything but you can still walk into a brick wall.
Like, type references, oh my god what the fuck.
@ohmrun I honestly don't mind the language itself. It's just that it gets way harder to interface with it when you're using JS dependencies or trying to do stuff that works best with JS but is a huge pain in the ass to represent in TS.
There's no good way to write externs, it's futile.
I feel like a pure TS workflow with Deno would be less annoying to deal with compared to slapping it onto node.js and the node_modules workflow. 🤔