Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Program your next server in Go

talks.golang.org

Post reply on HN
Print view View original

11–20 of 384 posts

Re: Program your next server in Go

#11

Post by muraiki »

tokenizerrr wrote: post #6

What about debugging? This is the major pain point for me. I've tried using GDB, but... > GDB does not understand Go programs well. The stack management, threading, and runtime contain aspects that differ enough from the execution model GDB expects that they can confuse the debugger, even when the program is compiled with gccgo. As a consequence, although GDB can be useful in some situations, it is not a reliable deb…

Have you tried out Delve? https://github.com/derekparker/delve

I've only used it for simple cases, so I don't know if it helps with your criticisms, but it was designed for Go. I mention this because it seems like many gophers aren't aware of Delve.

Re: Program your next server in Go

#12

Post by bboreham »

woah wrote: post #9
tokenizerrr wrote: post #6

What about debugging? This is the major pain point for me. I've tried using GDB, but... > GDB does not understand Go programs well. The stack management, threading, and runtime contain aspects that differ enough from the execution model GDB expects that they can confuse the debugger, even when the program is compiled with gccgo. As a consequence, although GDB can be useful in some situations, it is not a reliable deb…

Visual Studio Code has a visual debugger that is close to being on-par with Chrome's JavaScript debugger, at least for me.

And it works with Go, resolving some or all of the issues mentioned?

Re: Program your next server in Go

#14

Post by tokenizerrr »

muraiki wrote: post #11
tokenizerrr wrote: post #6

What about debugging? This is the major pain point for me. I've tried using GDB, but... > GDB does not understand Go programs well. The stack management, threading, and runtime contain aspects that differ enough from the execution model GDB expects that they can confuse the debugger, even when the program is compiled with gccgo. As a consequence, although GDB can be useful in some situations, it is not a reliable deb…

Have you tried out Delve? https://github.com/derekparker/delve I've only used it for simple cases, so I don't know if it helps with your criticisms, but it was designed for Go. I mention this because it seems like many gophers aren't aware of Delve.

I certainly wasn't aware of Delve. But I also haven't Go'd in a while now. Looks promising.

Re: Program your next server in Go

#15

Post by tokenizerrr »

bboreham wrote: post #12
woah wrote: post #9

Earlier quoted context omitted.

Visual Studio Code has a visual debugger that is close to being on-par with Chrome's JavaScript debugger, at least for me.

And it works with Go, resolving some or all of the issues mentioned?

I just looked it up, and it integrates with Delve. So it looks promising.

Re: Program your next server in Go

#18

Post by squiguy7 »

> Clarity is critical.

When you need to write high performance code this is a great maxim. I enjoy the simplicity of Go and the guarantees it provides. Being able to reason about code and not having to guess is a win for any development team.

Post reply on HN