You'll still be able to use the performance gains of this Go port to transpile TypeScript on top of JavaScript, right?

[mikegwhit]

If I understood the news correctly -- effectively -- the demonstrated 10x gains of the Go port will be achieved for TypeScript in Go and end-users will be able to reap the benefits of faster transpilation speed using the Go port but the end-users may still be using their existing TypeScript codebases written in JavaScript. In other words, everything is still as it has been except now running tsc for example is 10x faster. If, for example, an organization were to decide to port their codebase to Go: they might experience similar runtime speed gains while gaining the the benefits of using TypeScript.

Is this all correct? Will this transpile TypeScript in JavaScript to Go?

[mikegwhit]

See #454 (reply in thread) which seems to indicate that yes, this just affects how tsc itself may be run, but presumably the latter part of my assertion is likewise true.

Further guidance appreciated just tagging any answers I find.

[jakebailey]

This is just about tsc, tsserver, etc. We did not write a tool that can convert arbitrary JS/TS to Go.