A month ago I switched to Google Reader from NetNewsWire because I was tired of the cross computer synchronization problem. Reader is also one of those nice applications that doesn't just ape its desktop predecessors— perhaps because there isn't a real strong legacy of desktop RSS readers— but that instead tries to make the whole experience of consuming feeds more web native by weaving in social features around the sharing of posted items. I'll have a lot more to say about mixing together feed management and social features over the next few days (as I am on vacation and will have finally have a chance to write about friends, feed management, and the secret of Facebook's success) so for now I will just say that Reader is a good application that anyone interested in going beyond very basic feed consumption should definitely check out.
This post is not about Reader though, but about Google Gears, a new browser plug-in that was released recently around Google's first Developer Day to make it possible to take web applications offline. Basically Gears combines 3 things together in a local runtime: an RDBMS (SQLite), a local web server, and a multi-threading primitive in the form of a worker pool. The plug-in (which currently runs on IE and Firefox and sort of supports WebKit/Safari) provides these three services and leaves the rest to you, the developer.
I have to admit that when I first read about Gears, I was a bit disappointed that Google had chosen to bite off so little in order to solve what is probably the Achilles heel of all web applications, offline use. If solving this problem had fallen to me (which it did in a small way 7 years ago when we were building a bandwidth-enhancing service for the Memora Personal Server), I would also have used a local webserver but made it capable of running server code (in the form of Java/PHP/Python/Ruby plug-ins) and capable of transparently rewriting URLs so that the enduser was unaware of which server was actually handling the request while the developer had less work to do in building out hybrid applications. We pulled this trick off at Memora to serve big video files from a local webserver instead of across the network when the assets existed in both places with the best part being that outside of a bit of middleware which the developer had to be conscious of in certain cases, the rest of was completely transparent.
That said yesterday I got my first chance to test Gears via a synced version of Reader that went "offline" with 755 of my most recent posts for a long airplane ride. Holy smokes, that thing is fast! Though it could have quite a bit to do with the way that Reader itself is architected, the best part of using Reader offline is that you don't have to wait for the server loads as a new bunch of posts is loaded in. It just screams. By comparison, I've got a single user instance of the entire Tabblo website running on my machine for development purposes (MySQL, Apache C modules, Python, Django) and it is much much slower despite having no real server load, so much so, that I'm beginning to think that there may be quite a bit of connection setup/teardown overhead between a web browser and even just a local server, and that the Google guys may have been conscious of this in the design of Gears.
Gears is not without some enduser annoyances that are imposed on it by the browser, the biggest one being that you have to remember to leave the browser window open before you go offline or you're stuck despite the plug-in having all of the data anyway. There is also of course the nasty problem of distribution; despite the fact that it's provided as a smallish .xpi or ActiveX control, it would be a whole lot better if it could come pre-bundled with the browser, or at the very least with the Google Toolbar. There is zero doubt in my mind that Gmail is going to get a Gears life any day now, something which will likely remove the last obstacle for my going to it full time for all of my email needs, so perhaps there are plans to address both of these issues.
In the meanwhile, I can't wait to try using Gears for a project as it's clear that the Gears folks have done a very nice job of doing a UNIX (little small tools that can provide big leverage) to a key piece the "webapps all the time and everywhere" challenge we're all dealing with these days.