News for hackers. Stuff that matters.
Re:The State of Go: Where we are in February 2016 by blakeyrat on Wednesday February 03, 2016 @04:17PM (#11029834)
Great tooling? Does Go have any quality IDEs with integrated debuggers yet?

I feel that open source developers mean something entirely different with the phrase "great tooling" than developers used to Visual Studio would mean. :)

Re:The State of Go: Where we are in February 2016 by geodel on Wednesday February 03, 2016 @05:58PM (#11030576)
Absolutely! They do not mean big GUI based IDE when they say tooling. Infact this is why Go will remain unviable option to .net developers. Go is likely to be much more popular among dynamic languages users and even some Java developers who are tired of enterprisey bloat.
Re:The State of Go: Where we are in February 2016 by twotwotwo on Thursday February 04, 2016 @05:10PM (#11037709)
https://github.com/visualfc/liteide exists with, basically, many of the same things as you see people augment vim, etc. with (autocomplete, format on save, etc.) but a GUI editor. It has interactive debugging, but I don't use it so I dunno how it is. I can't promise you'll like it, but I dig it for some uses and it's there. The GUI itself seems to be maintained by one developer and as such it is unlikely to ever have full feature parity with Visual Studio. :)
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.

Re:The State of Go: Where we are in February 2016 by jmgao on Wednesday February 03, 2016 @07:46PM (#11031154)
Does go even have any good command-line debuggers? All of the things I've seen either involve insanity like preprocessing your source to inject hooks in between each line of code, or don't actually work.
Re:The State of Go: Where we are in February 2016 by pjspycha on Wednesday February 03, 2016 @11:36PM (#11032015)
Delve is an open source debugger for go. And many editors can work with delve such as Visual Studio Code. There is an animated gif of the debugger on the vscode-go page. https://github.com/derekparker/delve https://github.com/Microsoft/vscode-go
Re:The State of Go: Where we are in February 2016 by pjmlp on Thursday February 04, 2016 @03:13AM (#11032652)
Due the way Delve rewrites Go source code and relies on having it available, I wouldn't call it a debugger.