Hacker News new | ask | show | jobs
by the_mitsuhiko 466 days ago
> The Go choice over Rust/C# reveals something deeper: Microsoft prioritized shipping a working solution over language politics. Go's simplicity (compared to Rust) and deployment model (compared to C#) won the day.

I'm not sure that this is particularly accurate for the Rust case. The goal of this project was to perform a 1:1 port from TypeScript to a faster language. The existing codebase assumes a garbage collector so Rust is not really a realistic option here. I would bet they picked GCed languages only.
2 comments
whazor 466 days ago
Also explained in the FAQ: https://github.com/microsoft/typescript-go/discussions/411
link
pc86 466 days ago
I can't imagine the devs at Microsoft have any issues with C#'s "deployment model."
link
Yoric 466 days ago
I can imagine C# being annoying to integrate into some CIs, for instance. Go fits a sweet spot, with its fast compiler and usually limited number of external dependencies.
link
giancarlostoro 466 days ago
I assume they picked Go because the binaries can be very stand alone.
link