Re:The State of Go: Where we are in February 2016
by pjmlp on Thursday February 04, 2016 @03:17AM
(#11032662)
> Infact this is why Go will remain unviable option to .net developers.
Why should we even bother with Go, if we have C#, F#, JIT, AOT compilation to dynamic binaries (NGEN), AOT compilation to static binaries (.NET Native), NuGET already available?
And yes, I do know Go and even tried some early contributions before the 1.0 release.
For me it is only a step forward for C developers.
Still a very important one, as we need more widespread use of safer compiled languages.
Why should we even bother with Go, if we have C#, F#, JIT, AOT compilation to dynamic binaries (NGEN), AOT compilation to static binaries (.NET Native), NuGET already available?
And yes, I do know Go and even tried some early contributions before the 1.0 release.
For me it is only a step forward for C developers.
Still a very important one, as we need more widespread use of safer compiled languages.