When picking a language for your next project, few things are more critical than the tooling it provides. In this article, Ayooluwa Isaiah wraps up our Go for Rubyists series with an introduction to go tooling.
These days fewer and fewer web developers get to specialize in a single language like Ruby. We use different tools for different jobs. In this article, Ayooluwa Isaiah argues that Go is the perfect complement to Ruby. The developer who knows both is in a great position to handle almost any back-end challenge.
Go has built-in features to make it easier for programmers to implement logging. Third parties have also built additional tools to make logging easier. What's the difference between them? Which should you choose? In this article Ayooluwa Isaiah describes both of these and discusses when you'd prefer one over the other.
Last week we released some improvements to our Go client, which reports panics and errors from Go applications. You can now configure the client to ignore errors in development/test mode.
This week we released some improvements to our Go client, which reports panics and errors from Go applications.
Go is such a new language that even more established frameworks can have interesting quirks. One of the key issues learning the Go framework is the availability of useful documentation. Unfortunately, Go framework maintainers don’t always prioritize writing the documentation necessary to get new programmers up to speed on their frameworks. The five frameworks below, however, have usable documentation and are straightforward to use.