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

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 and sa…

Managing dot-files with vcsh and myrepos

Say I want to get my dot-files out on a new computer. Here's what I do:

# install vcsh & myrepos via apt/brew/etc
vcsh clone https://github.com/tfnico/config-mr.git mr
mr update

Done! All dot-files are ready to use and in place. No deploy command, no linking up symlinks to the files. No checking/out in my entire home directory as a Git repository. Yet, all my dot-files are neatly kept in fine-grained repositories, and any changes I make are immediately ready to be committed:

config-atom.git
    -> ~/.atom/*

config-mr.git
    -> ~/.mrconfig
    -> ~/.config/mr/*

config-tmuxinator.git  
    -> ~/.tmuxinator/*

config-vim.git
    -> ~/.vimrc
    -> ~/.vim/*

config-bin.git   
    -> ~/bin/*

config-git.git          
    -> ~/.gitconfig

config-tmux.git  
    -> ~/.tmux.conf    

config-zsh.git
    -> ~/.zshrc

How can this be? The key here is to use vcsh to keep track of your dot-files, and its partner myrepos/mr for operating on many repositories at the same time.

I discovere…

The End of GitMinutes (my podcast)

I'm just about ship GitMinutes episode 46, which is going to be the final episode. I'll just paste the outro script here, as it sums up the sentimental thoughts pretty well:

I’m happy to have finally finished [publishing the last episodes from Git-Merge 2017], just in time before Git-Merge 2018 takes place in March. I won’t be going there myself, so I’m counting on someone else to pick up the mic there.

It’s sad to be shipping this one as it is probably the last GitMinutes episode ever. To go a bit down memory lane, 6 years ago, my daughter was born, and as I used a little of that paternity leave to set up my podcasting infrastructure and produce the first few episodes. Initially it was just going to be 10 episodes and call the experiment finished. Instead, I got to 46 episodes, the last dozen or so lazily tailing the last few Git-Merge conferences.

To every one of my guests, thank you so much again for coming on to share your passion in this little niche of computer science a…

Joining eyeo: A Year in Review

It's been well over a year since I joined eyeo. And 'tis the season for yearly reviews, so...

It's been pretty wild. So many times I thought "this stuff really deserves a bloggin", but then it was too inviting to grab onto the next thing and get that rolling.

Instead of taking a deep dive into some topic already, I want to scan through that year in review and think for myself, what were the big things, the important things, the things I achieved, and the things I learned. And then later on, if I ever get around to it, grab one of these topics and elaborate in a dedicated blog-post. Like a bucket-list of the blog posts that I should have written. Here goes:
How given no other structures, silos will grow by themselves This was my initial shock after joining the company. Only a few years after taking off as a startup, the hedges began growing, seemingly almost by themselves, and against the will of the founders. I've worked in silos, and in companies without the…

Always use git-svn with --prefix

TLDR: I've recently been forced back into using git-svn, and while I was at it, I noticed that git-svn generally behaves a lot better when it is initialized using the --prefix option.

Frankly, I can't see any reason why you would ever want to use git-svn without --prefix. It even added some major simplifications to my old git-svn mirror setup.

Update: Some of the advantages of this solution will disappear in newer versions of Git.

For example, make a standard-layout svn clone:

$ git svn clone -s https://svn.company.com/repos/project-foo/

You'll get this .git/config:

[svn-remote "svn"]
        url = https://svn.company.com/repos/
        fetch = project-foo/trunk:refs/remotes/trunk
        branches = project-foo/branches/*:refs/remotes/*
        tags = project-foo/tags/*:refs/remotes/tags/*

And the remote branches looks like this (git branch -a):
    remotes/trunk
    remotes/feat-bar

(Compared to regular remote branches, they look very odd because there is no remote name i…