JSDoc is much more cumbersome than using TypeScript. That's it. It clutters the code in a way that TypeScript somehow avoids. TS types are smoothly integrated in the code itself, IMO. Not as much the case with JSDoc.

[–] biggeoff@sh.itjust.works 4 points 15 hours ago (2 children)

Thanks! As a hardware guy it'll be a long time before I do anything with this information. Nice to hear the opinions of actual Devs.

[–] moseschrute@lemmy.world 2 points 12 hours ago (1 children)

I suspect most Lemmy users hating on JS haven’t done much professional JS work. Especially these days with TypeScript and all the modern conveniences.

I’m curious, what kinda hardware do you work on?

[–] biggeoff@sh.itjust.works 1 points 8 hours ago

Digital hardware, mainly top-level design in verilog and associated checks using python/perl (sad)

Right now working on a GPU which is fun!

[–] victorz@lemmy.world 1 points 13 hours ago (1 children)

Ah alright 🙂 My pleasure! Yeah I wouldn't even consider JSDoc if I had the choice of TypeScript. I even did some years of Advent Of Code in TypeScript. It's performant enough and simple to employ some kind of quasi functional programming style with it. I think it's great.

[–] moseschrute@lemmy.world 1 points 12 hours ago (1 children)

I think Rich Harris famously migrated Svelte from TypeScript to JSDoc, while still supporting TypeScript via JSDoc. I don’t use Svelte, so I have no idea how well this works in practice. However, Rick Harris seems smart to me, unlike other overly opinionated devs like DHH. I still wouldn’t use JSDoc over TS, but I guess if it works for your project, who cares. What matters is that we all remember the one true enemy, DHH

[–] victorz@lemmy.world 2 points 11 hours ago

I would actually love to hear the rationale behind migrating from TypeScript to JSDoc. Mind boggling to me.

Especially nowadays when there is promising work towards very fast, Rust-based TypeScript tooling, which web devs are in love with.

So yah, very interesting.

But yeah, DHH 🖕🖕