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.
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.
Trusting your own judgement on ‘AI’ is a huge risk
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