[rixtox]

I remember arguing with Ron on the TC39 disposable proposal that I think Go's `defer` is a better pattern than C#'s `using`, and he tried to convince me the otherwise.

I was surprised to see they choose Go instead of C# for the TypeScript compiler port. Microsoft has been trying to make ECMAScript look more similar to C#, and their Windows Universal SDK has made a lot of efforts to provide a seamless transition for developers to port their code between C# and TypeScript. And yet they still think porting TypeScript compiler to Go is easier to do than porting it to C#.

Despite my different tech view with Ron, I appreciate and respect the great work he has done to TypeScript & ECMAScript. And I wish him the best with his next adventure.

[dahauns]

Hejlsberg's arguments for choosing go over c# sounded well founded and very pragmatic to me though, with things like battle tested AOT compilation (.NETs current iteration is very promising, but still relatively nascent) and the type system being a stronger fit (I really miss TS's structural typing sometimes in C# :) ).

As someone who has a lot of .NET projects at work it's a bit of a bummer since the dogfooding would have been a huge benefit for .NET, but I honestly can't argue with their choice.