News for hackers. Stuff that matters.

A comment on A 10x Faster TypeScript. Parent comment

Re:A 10x Faster TypeScript by dimgl on Tuesday March 11, 2025 @11:27AM (#43333430)
C# needs an interpreter (.NET runtime) while Go compiles down to a binary. And the toolchain allows you to compile for other architectures fairly easily.

So that could be a fundamental reason why.

[ Parent | on HN ]
Re:A 10x Faster TypeScript by rat9988 on Tuesday March 11, 2025 @11:31AM (#43333466)
The grand parent was talking about AOT.
[ Parent | on HN ]
Re:A 10x Faster TypeScript by bitwize on Tuesday March 11, 2025 @11:35AM (#43333503)
.NET has AOT compilation now. There really is no excuse, especially when you consider that C# has a pretty decent type system and Go has an ad-hoc, informally specified, bug-ridden, slow implementation of half of a decent type system.
[ Parent | on HN ]
Re:A 10x Faster TypeScript by dimgl on Tuesday March 11, 2025 @11:45AM (#43333627)
> Go has an ad-hoc, informally specified, bug-ridden, slow implementation of half of a decent type system.

It's not lost on me that this is a widely used aphorism. The problem is that it's not true in any way shape or form.

[ Parent | on HN ]
Re:A 10x Faster TypeScript by mervz on Tuesday March 11, 2025 @12:44PM (#43334343)
It absolutely is... Go's type system is an abomination.
[ Parent | on HN ]
Re:A 10x Faster TypeScript by nipah on Tuesday March 11, 2025 @04:21PM (#43336602)
Let's not assume C#'s type system is THAT much better, it is also a mess in dozens of cases and is hardly pleasant from a DX standpoint.
[ Parent | on HN ]
Re:A 10x Faster TypeScript by madeofpalk on Tuesday March 11, 2025 @12:56PM (#43334519)
People using pointers when they want to hack in null values points towards a problem in Go's type system.
[ Parent | on HN ]