After hearing the explanation about why he picked Go for the Typescript compiler I can only be more of a fan of Anders Hejlsber.

He said that Go was chosen due to its suitability for the workload, offering low-level control, optimized native code, automatic memory management, and concurrency.

And this coming from the same guy that created C#, Typescript, Delphi & Turbo Pascal shows how a real engineer takes a decision of this magnitude.

Is Go the best decision for every SW project? No, but in this case the arguments (and the tests they did during their evaluation) check out.

And no, picking F# simply because you love the language is not a mature decision.

You can check his arguments here:

https://www.youtube.com/watch?v=pNlq-EVld70

I know, you are telling the fisher how to fish.

See the BUILD 2025 talk, where he explains the data structures redesign to fit into Go's lesser type system.