Dropping support for ruby1.8

This is motivated by a failing test suite in TravisCI, but it seems
reasonable given that ruby2.0 is already out.

It will also allow us to make use of ruby1.9 features without worrying
about backwards compatibility.