News for hackers. Stuff that matters.
Re:How We Went from 30 Servers to 2: Go by tptacek on Wednesday March 13, 2013 @01:00AM (#5366900)
Comments like this are weird. Go does not like exceptions. They've built a whole idiom around error returns. When you said, "I need exceptions", what did you expect them to say? "Oh, sorry, we forgot that, we'll get right on it"?

I also don't understand what you mean by "interactive debugger". What is gdb if not an interactive debugger? Gdb is my go-to debugger for Ruby as well.

Re:How We Went from 30 Servers to 2: Go by trungonnews on Wednesday March 13, 2013 @02:19AM (#5367122)
Something like RubyMine IDE debugger or Firebug javascript debugger.

If you are a Ruby developer then I highly recommend trying out RubyMine. I promise that you will never debug Ruby code using gdb again!

Re:How We Went from 30 Servers to 2: Go by kragen on Wednesday March 13, 2013 @07:40PM (#5371914)
I got all excited when I saw your comment and went and checked out the latest RubyMine video on YouTube, because having something like Firebug for Ruby would be awesome. But it looks just like what gdb gives you when being driven by a graphical frontend like DDD or Emacs. Actually it looks a lot less powerful than DDD. What am I missing?
Re:How We Went from 30 Servers to 2: Go by irahul on Wednesday March 13, 2013 @05:21AM (#5367525)
> Something like RubyMine IDE debugger or Firebug javascript debugger.

That's not for the go team to develop.

> If you are a Ruby developer then I highly recommend trying out RubyMine. I promise that you will never debug Ruby code using gdb again!

I haven't used RubyMine, but I have used Visual Studio and Eclipse debuggers, and I still debug using gdb, ruby-debug, pdb et al.

Re:How We Went from 30 Servers to 2: Go by irahul on Wednesday March 13, 2013 @05:23AM (#5367531)
> Gdb is my go-to debugger for Ruby as well.

Unless you are debugging the ruby process(and not the running script), what does gdb buy you over ruby-debug?