TypeScript Debate

Enterprise frontend and backend development, all Typescript. TS is easily the most productive language I've ever used (professionally worked in Java, then Javascript, with some Ruby and PHP). It scales from no-types JS to architecture astronaut seamlessly. You only have to use what's useful to you. My only hangups were esoteric type errors, but AI made this go away (mostly with more specific explanations of the issue).We ported our webapps from JS to Typescript a while back, and

You don't like TypeScript?

I work with typescript everyday. I review prs, i mentor junior devs that are learning typescript. Ofcourse this is my experience, maybe yours is different, if so please tell me about it. The only thing i said is that there is an upfront cost in velocity that people are usually not considering when they are choosing to use ts over js. Sure, that cost may be amortised in fewer bugs and easier collaboration across large development teams. But i see people struggling everyday with specifying correct

TypeScript development on VScode is excellent (I'm told) so that would be a reason for this.Excellent tooling exists for you if your language is TypeScript, so maybe try putting TypeScript in more places.

TypeScript did a good enough job that no-one need bother again.

As someone coming from Ruby to TypeScript, I find types cumbersome, verbose, complex, and not of much use. I have been writing and reading TS for the past six months. What am I missing?

That's ignoring all the negative effects of using typescript.

This reads like knee-jerk reaction from someone who's never tried TypeScript.

Perhaps give it another try, but with TypeScript. Im a front end dev and yes, I feel the JS pain. I look back at how I used to do things and think "wtf". TS completely changed this and brought it back to sanity.

have you even tried to use TypeScript on a real project to say something like that ?