TypeScript is being ported to Go | interview with Anders Hejlsberg

[Paulo Pinto]

On Friday, 14 March 2025 at 16:47:35 UTC, Derek Fawcus wrote:
> On Friday, 14 March 2025 at 15:04:15 UTC, Robert Schadek wrote:
>> On Wednesday, 12 March 2025 at 13:05:05 UTC, Sergey wrote:
>>
>>> Oh and "we also need a great tooling" maybe not the best for 
>>> D.. idk how good is support of vscode for Go but I assume it 
>>> should be good
>>
>> My interest was not so much about them using go instead of D, 
>> but more about
>> them moving into a compiler server architecture. Aka. not 
>> recompiling their std.stdio on every compile.
>
> What I found interesting was the semi-machine translation; and 
> that if one looks at the github ticket with the discussion, the 
> post-port code looks so similar to the pre-port code.  So 
> vindicating the choice of Go as the target.
>
> Also the shear degree of whining on the ticket from folks who 
> wanted it ported to C# instead, "because"...

As one of those whining folks, imagine having Walter after all 
these years, suggesting that his next side project is going to be 
in Zig/Rust instead of D.

That is why those of us that like C#, and experience the adoption 
hurdles outside Windows still being a big problem, see having the 
C# original architect suggesting something else, that also 
happens to contradict .NET team marketing efforts.

Having such a key figure in the programming world adopting Go, 
for what is one of the most used frontend toolchains, will only 
solidity even further Go's relevance in the industry, beyond 
Docker and Kubernetes ecosystem.

Thus making .NET team developer advocacy efforts even harder.