> You can't run it with JS runtimes, and it has features JS will never have. It's definitely transpiled.
AFAIK TypeScript has a grand total of one non-typesystem related feature which doesn't already exist in JS (or as an ES proposal) - enums[1]. All the other parts of TypeScript can be transpiled just like Flow - by stripping away the type annotations.
That's a bizarre comment from someone who just said they're dedicating their career to transpiling. Flow is a layer of safety on top of JavaScript, while TypeScript is a different language. You can't run it with JS runtimes, and it has features JS will never have. It's definitely transpiled.
See also: Elm, ClojureScript, NativeScript, PureScript, Haxe, and the staggering number of transpile-X-to-JavaScript projects out there.
> but for general app development it's better to have a GC and the other high-level features JS has that wasm doesn't
The features that are missing from wasm can be implemented in the original language. Rust, at least, doesn't have garbage collection. There are also multiple proposals to add garbage collection to wasm.
> That just means some people want wasm to take over, for that one specific reason. It doesn't mean it's actually going to gain traction to evolve in that direction.
People wanting something to happen is all that's needed to make it happen. If you concede people will want it, then you concede it will happen. wasm replacing JS as the API for the browser makes more sense than, say, JavaScript on a server, and yet here we are...