Skip to main content

Finally a Book on Google Guava

Well, this was about time:

Google Guava at PacktPub
TL;DR: There's a little book about Guava out. I've had a quick look through it and it looks mighty fine.

Earlier this week I got an offer to review this new book on Google Guava. For those of you who don't know Guava, I dare say it is the finest utility tool-belt library available for Java development.

The author, Bill Bejeck, hasn't been involved with the development of Guava, but he has blogged some articles on the subject in the past. What I've read so far in the book speaks that he knows what he's talking about.

Why do you need a book about Guava?

Now, Guava is a library where you can only fully immerse yourself by reading through all of the JavaDoc, and in the first few rounds of doing so you probably won't understand half of it.

What you can do instead, for starters, is to read through the GuavaExplained wiki pages, which offer a much nicer reading experience, but go into very little detail.

So then you're left with looking through some presentations/slides from the authors, which are not really meant for being read, or you look through some of the articles and blog-posts scattered around the net (I used to collect them all here, but I left it behind at some point. Maybe I should put the list on GitHub instead soon).

The problem with any given article of Guava is that it focuses on just a few things. Usually something with the collections, filtering and ordering. Not many articles go into for example concurrency, or file IO, and none of them cover everything.

When facing some programming challenge, you often don't know whether it is somehow solved within Guava, or whether it can be solved with the help of Guava. So you start looking for it. If you're lucky, the words you choose to search for are coincidentally used in a post on StackOverflow, but often you end up scurrying around in the Guava JavaDocs not knowing in which class your desired utility is located.

Solution: This book gives you a terse but elaborate tour of all the most important sides of Guava. It gives you knowledge of a lot of great features, and gives you many ideas of what other things you should look for in Guava when facing some problem.

Inside the book

Just to put it into perspective. I've been using Guava since 2010, and only half-way through the book it turned to things I'm still unfamiliar with. Already in the first chapter I discovered new things about the Joiner and Splitter I wasn't aware of.

I'm not going to duplicate the table of contents here, just head over to the book homepage and see the respective tab there. Apart from covering the Guava basics for Strings, objects, collections, streams and IO, there are some really interesting advanced sections on caching, concurrency and event-based programming (the EventBus class). I'm looking forward reading these parts more thoroughly over the next weeks.

One downside of the book is that it's arriving very near to the time where we will finally get lambdas into Java with Java 8. Don't be alarmed though, the book will still be useful. Actually, closures in Java are an excellent fit for Guava's functions, and will make them much easier to write and read. The author himself explains how this works out in this blog-post. So it's a bit of a pity that the book wasn't able to make use of the new syntax. Perhaps he will publish a Java 8 version of the code examples in the future (natch, natch)?

Another thing mentioned in the book is Guava's Optional type, but there is no discussion on this versus the Optional type coming with Java 8. Another thing I missed was a mention of the Throwables.propagate methods, which are great for quickly dealing with checked exceptions, but then again, there are limits to what you can cover in a book of roughly 100 pages.

Reading experience

I got the .epub version on my Android tablet, and the best reading experience was in Google Play Books where there was some coloring of headings, and source code was different color from the text of the book.

Some of the code examples get some indenting and line breaks wrong, but maybe this is a common problem with programming eBooks these days. I mean, why is there no colored syntax highlighting for code in eBooks? In any case, once you buy the book you can download all the sample code from every chapter that are ready to build with both Maven and Gradle.

Summary

This is a great and important little guide with little competition. It delivers on the whole "Getting Started" premise really well in quite few pages, and works well as both a reference to have around when programming Java, and as a thorough read of getting into what Guava is about. Well done!

Comments

Popular posts from this blog

Open source CMS evaluations

I have now seen three more or less serious open source CMS reviews. First guy to hit the field was Matt Raible ( 1 2 3 4 ), ending up with Drupal , Joomla , Magnolia , OpenCms and MeshCMS being runner-ups. Then there is OpenAdvantage that tries out a handful ( Drupal , Exponent CMS , Lenya , Mambo , and Silva ), including Plone which they use for their own site (funny/annoying that the entire site has no RSS-feeds, nor is it possible to comment on the articles), following Matt's approach by exluding many CMS that seem not to fit the criteria. It is somewhat strange that OpenAdvantage cuts away Magnolia because it "Requires J2EE server; difficult to install and configure; more of a framework than CMS", and proceed to include Apache Lenya in the full evaluation. Magnolia does not require a J2EE server. It runs on Tomcat just like Lenya does (maybe it's an idea to bundle Magnolia with Jetty to make it seem more lightweight). I'm still sure that OpenAdvant

What I've Learned After a Month of Podcasting

So, it's been about a month since I launched   GitMinutes , and wow, it's been a fun ride. I have gotten a lot of feedback, and a lot more downloads/listeners than I had expected! Judging the numbers is hard, but a generous estimate is that somewhere around 2000-3000 have listened to the podcast, and about 500-1000 regularly download. Considering that only a percentage of my target audience actively listen to podcasts, these are some pretty good numbers. I've heard that 10% of the general population in the western world regularly listen to podcasts (probably a bit higher percentage among Git users), so I like to think I've reached a big chunk of the Git pros out there. GitMinutes has gathered 110 followers on Twitter, and 63, erm.. circlers on Google+, and it has received 117 +'es! And it's been flattr'ed twice :) Here are some of the things I learned during this last month: Conceptually.. Starting my own sandbox podcast for trying out everythin

Encrypting and Decrypting with Spring

I was recently working with protecting some sensitive data in a typical Java application with a database underneath. We convert the data on its way out of the application using Spring Security Crypto Utilities . It "was decided" that we'd be doing AES with a key-length of 256 , and this just happens to be the kind of encryption Spring crypto does out of the box. Sweet! The big aber is that whatever JRE is running the application has to be patched with Oracle's JCE  in order to do 256 bits. It's a fascinating story , the short version being that U.S. companies are restricted from exporting various encryption algorithms to certain countries, and some countries are restricted from importing them. Once I had patched my JRE with the JCE, I found it fascinating how straight forward it was to encrypt and decrypt using the Spring Encryptors. So just for fun at the weekend, I threw together a little desktop app that will encrypt and decrypt stuff for the given password

The academical approach

Oops, seems I to published this post prematurely by hitting some Blogger keyboard shortcut. I've been sitting for some minutes trying to figure out how to approach the JavaZone talk mentioned in my previous blog-post. Note that I have already submitted an abstract to the comittee, and that I won't publish the abstract here in the blog. Now of course the abstract is pretty detailed on what the talk is going to be about, but I've still got some elbow room on how to "implement" the talk. I will use this blog as a tool to get my aim right on how to present the talk, what examples to include, what the slides should look like, and how to make it most straightforward and understandable for the audience. Now in lack of having done any presentations at a larger conference before, I'm gonna dig into what I learned at the University, which wasn't very much, but they did teach me how to write a research paper, a skill which I will adapt into creating my talk: The one

Git Stash Blooper (Could not restore untracked files from stash)

The other day I accidentally did a git stash -a , which means it stashes *everything*, including ignored output files (target, build, classes, etc). Ooooops.. What I meant to do was git stash -u , meaning stash modifications plus untracked new files. Anyhows, I ended up with a big fat stash I couldn't get back out. Each time I tried, I got something like this: .../target/temp/dozer.jar already exists, no checkout .../target/temp/core.jar already exists, no checkout .../target/temp/joda-time.jar already exists, no checkout .../target/foo.war already exists, no checkout Could not restore untracked files from stash No matter how I tried checking out different revisions (like the one where I actually made the stash), or using --force, I got the same error. Now these were one of those "keep cool for a second, there's a git way to fix this"situation. I figured: A stash is basically a commit. If we look at my recent commits using   git log --graph --