News for hackers. Stuff that matters.
Re:A 10x Faster TypeScript by nwah1 on Tuesday March 11, 2025 @11:24AM (#43333388)
Also, this is surprising because this was presented and led by Anders Hejlsberg, who is the creator of both C# and Typescript.

If anyone should have picked C# it would be him.

Re:A 10x Faster TypeScript by dagw on Tuesday March 11, 2025 @01:13PM (#43334733)
Hejlsberg seemed quite negative when it came to cross platform AOT compiled C# in several comments he's made, hinting at problems with both performance and maturity on certain platforms.
Re:A 10x Faster TypeScript by zigzag312 on Tuesday March 11, 2025 @02:05PM (#43335326)
Projects like this are needed to improve C#'s cross platform AOT. Missed opportunity IMO.
Re:A 10x Faster TypeScript by ryanjshaw on Wednesday March 12, 2025 @03:39AM (#43340739)
Absolutely. Go is where it is because of the parent org's commitment to dogfooding it; strange that Microsoft is wasting this opportunity AND sending a negative message to .NET devs.
Re:A 10x Faster TypeScript by Cthulhu_ on Wednesday March 12, 2025 @05:02AM (#43341138)
Sure, but this team's focus is on Typescript, not C# / cross-platform AOT; there's only so much time in a day. Others can pick it up I'm sure.

But I think it's also an indication that Typescript may be bigger and more important for Microsoft than C#/.NET is at this time. It's definitely much more used than C# is according to this non-representative survey of Stack Overflow (https://survey.stackoverflow.co/2024/technology).

Re:A 10x Faster TypeScript by Cthulhu_ on Wednesday March 12, 2025 @04:59AM (#43341120)
At the same time, if anyone can make a language choice, it's him - the fact he didn't pick his own language is high praise for both himself and his neutrality, and the Go language.
Re:A 10x Faster TypeScript by aws_ls on Wednesday March 12, 2025 @07:14AM (#43342011)
Go compiler tooklit works very well on all the OSes. That would be a consideration.
Re:A 10x Faster TypeScript by nwah1 on Thursday March 13, 2025 @01:17PM (#43355375)
So does the .NET compiler. That is not the issue.