you are viewing a single comment's thread
view the rest of the comments
[–] 5 points 8 months ago (10 children)
  • [+] 9 points 8 months ago* (last edited 1 day ago) (9 children)
  • [–] 8 points 8 months ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 8 months ago* (5 children)

    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.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 8 months ago (2 children)
    tsc
    

    And now you're back to pure JavaScript.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 8 months ago* (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 8 months ago

    By default, doesn't tsc just 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.

  • source
  • parent