News for hackers. Stuff that matters.
Re:Go best practices, six years in by gkya on Sunday May 01, 2016 @04:43PM (#11607785)
> - debugging is way harder. Hope you like printf.

Can't you use gdb with Go? https://golang.org/doc/gdb

Re:Go best practices, six years in by spriggan3 on Sunday May 01, 2016 @04:48PM (#11607805)
The second you launch a Go routine, gdb becomes useless.
Re:Go best practices, six years in by gkya on Sunday May 01, 2016 @05:21PM (#11607905)
How do you debug then? (I'm not a Go coder, tho I'm familiar a bit with it)
Re:Go best practices, six years in by sacado2 on Sunday May 01, 2016 @06:01PM (#11608056)
Oh, that's simple. We gophers don't make any mistake. Ever. It makes our lives easier.
Re:Go best practices, six years in by jsmthrowaway on Sunday May 01, 2016 @11:02PM (#11608990)
This is wrong. The answer is obviously "Go is debugged in production with extensive logging," so I question whether you're actually a gopher.
Re:Go best practices, six years in by shurcooL on Sunday May 01, 2016 @05:51PM (#11608024)
See another answer in this thread, https://news.ycombinator.com/item?id=11607829.