Among other things, I learned that:
the powerful type system eliminates a large class of bugs the compiler eliminates the long name spaces (and the corresponding run-time look ups)
getters/setters actually lead to better compression
you can split the client side code in multiple, independently loaded modules
the pseudoclassical pattern used for OOP is actually better than the functional pattern (when combined with the Closure compiler)
you can easily extend the Compiler with extra features...
These sound very interesting - it'd be good to have an explanation of these points.
I'm always wary of posts like this. It's tagged as book review but there isn't much detail about the book in question. It is effusive in it's praise of the book but gives very little detail of why the book is good. And it contains two affiliate links to the book that it mentions. On second reading, it looks like a post that just exists to try to generate affiliate clicks for the book in question.
I like the Closure compiler but not its templating library or its dom library. The dom library is not abstract enough (you have to explicitly create dom elements) and I generate all my js files via my own php based templating library that is a lot more powerful and concise.
A great combination for the front end through is CoffeeScript + the Closure compiler + jQuery (or your favorite dom library).
I am not sold on the templating library either. But the Closure library is quite extensive and abstract. It contains tons of useful (and well designed) UI components and compares favorably to something like jQuery UI. On the other hand there is a higher barrier of entry due to the lack of adequate documentation.