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.
Sure, but with lots of generated code that’s going to be hard to be human readable and changeable. It’s definitely more work to add a feature to the code generated by the compiler, than to add a feature if the code was initially written in JavaScript.
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.
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.
And now you’re back to pure JavaScript.
Sure, but with lots of generated code that’s going to be hard to be human readable and changeable. It’s definitely more work to add a feature to the code generated by the compiler, than to add a feature if the code was initially written in JavaScript.
By default, doesn’t
tscjust output the source TS files with type info stripped? Worst case you run a formatter on that output and you’re done.There’s some nonstandard TS features like the iterator shim and decorators and such, but you don’t get those by default from what I remember.
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