Re:Eight years of Go
by hackerfromthefu on Sunday November 12, 2017 @12:18PM
(#15681548)
Have a look at .NET Native with .NET core, it support AOT compilation with GC, and a very fully featured language and cross platform targets.
see https://blog.rendle.io/what-ive-learned-about-dotnet-native/ https://stackoverflow.com/questions/29609993/difference-betw... https://docs.microsoft.com/en-us/dotnet/framework/net-native...
To be clear, I agree with you. I was just responding to the OP's claim that the Go community overwhelmingly rejects generics with my perception that at most 60% of the community feels that way. I am very much in favor of generics.
Re:Eight years of Go
by peoplewindow on Saturday November 11, 2017 @12:59PM
(#15677298)
What's the big need for an AOT native EXE for you? You just don't want to copy a directory tree instead of a single file?
Not OP, but I can't execute a directory tree. I always seem to need a runtime, and often additional libraries and a bunch of `$*PATH` munging so the compiler locates the _correct_ dependencies.
Re:Eight years of Go
by frankzinger on Sunday November 12, 2017 @02:24AM
(#15680051)
Performance is often the answer.
How useful they are depends greatly on what you are doing, and programmers do a great many different things. For many kinds of library development, they can save you massive amounts of time and code, and/or lead to much better performance vs the workarounds available.
I wonder how many people who prefer Go without generics are coming from C++ templates, or Java generics, vs C# or F# generics.