We built a website to visualize Omaha Public School's enrollment data. It was a blast to build, and not just because it helped answer burning questions of teammate, parent, and all-around cool guy Alex Gates. Alex wanted to know why his daughter's kindergarden class had 39 children in it when classes began.
Here's what I learned.
This was all Jerod Santo's fault.
So when Hack Omaha rolled around this year, Jerod and I decided to team up and try a language neither of us knew. His suggestion: Go - Google's new(ish) language. Juan Vazquez joined in, and a team based on ignorance was born.
Go's docs describe the language:
Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language.
Going to School
I spent some time learning the language, and the Go tour was my main source. Perhaps it's the Ken Thompson-inspired origins, but it was nice working with a language that didn't condescend to you and treat you as a programming neophyte. I often feel like this about other guide, such as _why's Poigniant Guide to Ruby.
A Vodka Martini, Chilled
At this point, we had an idea that an app would be Go serving up an API on the backend, and a web frontend running AngularJS. The Changelog also had a really helpful post outlining Go's web application ecosystem.
Go has an impressive standard library and can serve HTTP easily out of the box, but we decided to apply a framework to provide a little structure. We went with Martini; a Sinatra-esque library that is less than a month old, in a proud Hack Omaha tradition.
Our services ended up with this structure.
This should look similar to Sinatra and its bretheren. Martini gives you the objects you need (like a ResponseWriter) via parameterized Dependency Injection, which is super convenient.
JSON encoding, HTTP headers, enabling CORS, all worked out of the box.
I've heard it's also testable, but nary a unit test was written during the hackathon. I should have known better, based on my lessons from last time. That said, Go has testing built into the language, so it'll be there when we're ready.
Databases, GORM Style
Go has database operations built into the standard library; just bring your own database-specific adapter. We went with MySQL, which has a great Go adapter. And writing queries is lame, so we tried out an ORM called Gorm. This was a little more mature, as it was a full 6 weeks old.
Using Gorm is pretty simple: define a
struct with types named like your database columns:
And populate them:
ORMs are appealing, especially when your database tables are denormalized by design to allow simple querying. But the additional complexity Gorm brought might not have been worth it. ORMs are known as the Vietnam of Computer Science for a reason.
Throughout Friday and all of Saturday, we were unable to connect to the database using Gorm's classes. It wasn't until nearly midnight on Saturday that we were able to figure out the correct incantations to get MySQL and Gorm to pull in data.
Clearer documentation might have helped, but in the end it turned out to be mostly user error.
Error handling in Go is idiomatically performed by returning two values from a function: the result you were expecting and an
err value is null, things went great. Otherwise, you have an error that needs handling.
As we were connnecting to databases in Gorm, we weren't retrieving that second parameter; so we never knew we had a badly formed database URI, even though the library was begging to tell us.
Lesson: understand the idioms of a language you're futzing around with.
Go Fly a Kite
It wasn't all sunshine. Beyond database and library issues, here's a few problems I encountered with Go:
- I like functional collections, and using slices (Go's version of an array) in a functional manner proved impossible.
Go appears to have functions for
map, and others, but we never got them working. It appears that Go programmers are content to use
forloops for everything, which is what we ended up doing.
- Go provides strict checks at compile time. This includes failing the build when you have declared a variable or import that you haven't used. Normally I love these checks, but this proved more annoying than useful in the iterative environment of a hackathon.
- As a user of third-party libraries, Go's package management is great (simply type
go get github.com/packageand it's available). But I never figured how to split apart our single-file Go program into a decent structure. We settled on placing our
structs in one file, and everything else in another. They all shared the
mainpackage, as well.
So you won, right?
Nope. This project did.
So we should blame Go?
Nah. The Boards team had a better product, and changing our backend wouldn't have made the difference.
If anything, I'm ready to double down on Go for the next hackathon.
You get productivity out of the box with a great standard library, plus the performance of a natively-compiled app, plus a syntax that feels both classical and modern.