Closure Tools were recently released by Google to allow for others to use the same rich libraries that Google uses internally. Its used by Gmail, Google Docs and Google Maps, but interestingly also used by Google Wave. While they don’t actually announce that Closure is used in Wave, the view-source obfuscated mess from Wave does strongly show it.The reason why its use in wave is more interesting than most others is that Wave is in GWT, while the rest are pure JS. This implies that an interface to the Closure Library may be coming to GWT. While the interface doesn’t seem to be made from Closure, there are references to “closure_hashCode” and “goog.net.BrowserChannel”.

It seems that after a recent update to wave, with:public only shows the waves which are already in your inbox. A simple remedy is to use group:public@a.gwave.com instead of with:public. I found it on http://www.google.com/support/forum/p/wave/thread?tid=10eaba86d62c005c&hl=en

Screenshot

So I was reading through some long-ish articles, and logically, I stare at the scrollbar to get a rough estimation of where I am in reading it.

But, the horrible thing called comments and a gasp theme, makes the page appear FAR longer than the article. I think that browsers, with the new <section> <header> and whatever that’s in HTML5 should interpret these markings and create a smarter scrollbar like how Chrome does the statusbar with little yellow markings where occurances are found. There should be ones which indicate the end of the article, start of comments, etc.

And I’ve noticing how I’m talking about Google for just about every new post. I think that’s just abou where all the innovation is right now. Or at least all the innovation that I use and know about that gets popularized by media.