News for hackers. Stuff that matters.
Re:Go compiler: Initial support for concurrent backend compi... by 0xFFC on Friday April 14, 2017 @03:51AM (#14113194)
I got very interested in Go recently, but I have question, how do you do your debugging in Go? I am using VSCode, and although VSCode support for Go is the best support between editors, but there is no official support for debugging , it seems.
Re:Go compiler: Initial support for concurrent backend compi... by skj on Friday April 14, 2017 @06:54AM (#14113694)
I don't want to pretend debuggers aren't useful...

But I haven't used a debugger in at least ten years. Production Go for the past few.

I debug with good log messages.

Of course, not everyone's problems are exactly like mine, so I will believe you if you say it's necessary for your situation.

Re:Go compiler: Initial support for concurrent backend compi... by rantanplan on Friday April 14, 2017 @09:09AM (#14114213)
Think vast codebases that were created by many programmers that weren't you :D
Re:Go compiler: Initial support for concurrent backend compi... by baconizer on Friday April 14, 2017 @01:53PM (#14115899)
this reflects my team's experience, initially skilled programmers (from C# mainly) complains almost hourly about lack of IDE features, in particular - Debugging. 14 months in now with 9 major services in production, I hear no more conversation on this, and still no one yet bothered to setup dlv. 'Breakpoints', to our surprises, is not actually indispensable. Also I noticed positive cultural change around, we move faster and team talks about business problem solving more than programming itself, to a point I believe rich functionality IDE over complicated things we do here.
Re:Go compiler: Initial support for concurrent backend compi... by sjellis on Saturday April 15, 2017 @04:52AM (#14119985)
> Also I noticed positive cultural change around, we move faster and team talks about business problem solving more than programming itself, to a point I believe rich functionality IDE over complicated things we do here.

I think that this point about team conversations is incredibly important. Apart from Ruby, Go is the only language that I know where the technical conversations seem to consistently focus on the problem at hand, rather than coding concerns like the finer points of language features. The company that I work for does both Ruby and C#, and the difference in the conversations around the two is very noticeable.

Re:Go compiler: Initial support for concurrent backend compi... by im3s on Friday April 14, 2017 @03:55AM (#14113207)
I don't know about VSCode but I tried Gogland a few days ago and it has integrated debugging support
Re:Go compiler: Initial support for concurrent backend compi... by konart on Friday April 14, 2017 @04:41AM (#14113315)
Nothing is better than Gogland or their (JetBrans') plugin for IDEA.

You can also try https://github.com/derekparker/delve

Re:Go compiler: Initial support for concurrent backend compi... by kristianp on Friday April 14, 2017 @07:39PM (#14118319)
You can use Delve with Vs Code. There's instructions here:

https://github.com/Microsoft/vscode-go/wiki/Debugging-Go-cod...

I've used it for debugging unit tests. Very handy.

Re:Go compiler: Initial support for concurrent backend compi... by saturn_vk on Friday April 14, 2017 @05:04AM (#14113379)
I thought vscode used delve to do go debugging. Also, the vim-go plugin has a lot more useful features than the vscode one