31–34 of 34 posts
"Go ... ergomonics" "G# compiles straight to managed assemblies and runs on the modern .NET runtime" These two are nothing close because it completely misses Go's ergonomics of compilation to portable static-linked binaries. For language constructs, maybe they have similar ergonomics, but the language is not only constructs. You have to ship your programs somehow, and this is where requirement to ship both binaries a…
One of the things go makes it simple to do is help a reader understand which constructs belong to which package, since any use of external imports is prefixed by the package name. In go, if I don’t know a constructs definition, i know exactly where to look at and find it. When exploring a new language I won’t always setup an ide first. I just want to look at the documentation on my own. Heck, any language which requi…
And this is also one of its biggest problem, any package can take a good valid variable name that can’t be used without shadowing a package. If it only didn’t make the stupid, IMO, idea of casing for access modifiers and made struct Pascal then this wouldn’t have been a problem.
Earlier quoted context omitted.
.NET programs can be AOT compiled
I am well aware of that, given that I routinely ship such programs. Compiling ahead of time does not change the fact that the .NET runtime is orders of magnitude larger than a C runtime.