I think the difference here is that the original motivation for choosing Go over Rust was that Go was easier to port TypeScript to.
LLMs change the calculus a lot, the result seems faster, and it's possible that the TypeScript team might want to change directions. It'd be a big deal, but I bet they'll at least discuss it.
Given the Typescript compiler rewrites that keep popping up, Next.js has one, this is another one, Angular just announced they are also going with theirs, eventually there will some community pressure on how the team will proceed.
Note there is already a feedback post from them (currently top one), that they will need to react to this.
Do we know why? Is there some hole the official one isn’t filling? Seems like having 10 different compiler implementations would be a portability nightmare. Now I can’t guarantee my typescript is going to run the same on node/angular/whatever
LLMs change the calculus a lot, the result seems faster, and it's possible that the TypeScript team might want to change directions. It'd be a big deal, but I bet they'll at least discuss it.