Post

It's still incredibly pleasing to run through old projects converting TS into JS + JSDoc. I made the decision to cut out TS (excluding `.d.ts` files, they get a pass) from all my personal projects years ago and I'm still very much convinced that's the right move. TS as an authoring format ain't it.

20/8/26, 4:55 am2 reposts31 likes

Austin Gil

@austingil.com

21 Aug

Curious where you noticed the pros of jsdoc and the cons of TS? I never fully moved over to ts, but been considering it lately, so those would be very interesting

@cjaythecreator.bsky.social

20 Aug

TS people are going to read this like you just announced you’re removing seatbelts from cars

Ryan

@rschristian.dev

20 Aug

Types are still there, they just get out of my way and I am not forced to insert build steps if I don’t want them. The TS lang server is where the value resides and it is perfectly capable of consuming standard JSDoc type comments.

@cjaythecreator.bsky.social

22 Aug

Yeah, same here. I don’t hate types, I hate having to build a small bureaucracy around them

Passle ☭

@passle.dev

20 Aug

Based I use .ts files (for types only) instead of .d.ts files though because of:

Ryan

@rschristian.dev

20 Aug

Interesting. Usually I'd just copy the types over when needed, though I try to prefer shipping source modules when possible. I can't recall (intentionally) using `tsc` to generate files in 5 or 6 years at this point, I've found it's never very good at producing files, any files.