this post was submitted on 28 Jan 2026
29 points (100.0% liked)
Programming
24742 readers
356 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Wut
Yeah, that’s uhh… that’s technically true for very strange and specific definitions of “compatibility”… but it wildly misses the point of TypeScript. Not sure what he was thinking there.
Yeah node's
--experimental-strip-typesexposes the absurdity immediately. The only incompatibility is that it has type annotations.Also, like… the fact that it has a compiler. It’s like saying C is incompatible with assembly because you can’t yeet a .c file at an assembler.
I mean once you write your app in typescript, you can't "go back" to pure JavaScript, you'll always have to use the typescript compiler to generate JavaScript (of course you can rewrite it later again, but will take potentially lots of effort). I'm pretty sure that's what they meant with "incompatible". You are now locked into M$ ecosystem.
You're being too generous. Calling typescript a rewrite shows the author chose something as an example they clearly don't understand the first thing about.
Possible, yes