Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



.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.


> 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.


It absolutely is... Go's type system is an abomination.


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.


People using pointers when they want to hack in null values points towards a problem in Go's type system.


The grand parent was talking about AOT.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: