I'm just connecting fictitious dots here, but it seems a rather crafty move to launch a hotel search site in the midst of the Airbnb debacle. "Oh, I was going to use Airbnb, then I heard about so-and-so's experience with them and decided to book a hotel instead ... and oh look! A spiffy new hotel search service!"
Which reminds me--I think there was an article linked here on HN not long ago about Google's timing in releasing new products/features--can't find it now, but makes me wonder if Google doesn't keep a few projects in the wings, waiting for the opportune moment (i.e. best PR moment) to launch them.
I doubt it. Based on the number of sessions at Google IO this year for GWT (many) and the number of sessions for Closure (one?), I would say they were outwardly pushing GWT much more than Closure.
Reasons you might consider using Closure instead of something like jQuery, plain-old-js:
2. You find yourself needing namespaces that are easy to implement.
4. You've got too many js files (2+) and you want to only have one in production for faster page loading (use closure compiler)
5. You're building an application with a team of developers; closure helps create modular, well documented code
6. You want to build a snappy, client-side heavy application
I couldn't be happier.
My only complaint is it seems Closure development doesn't have the velocity that other projects like GWT have. Google, it seems, is putting it's money more on GWT than something like closure; or so it seems based on the amount of announcements for GWT, the quality of the tools and libraries being produced, the number of updates to closure compared to GWT. While GWT is a powerful tool, it's more complex (thanks to Java), harder to setup, harder to get started. In some ways I wish they would take the tools and frameworks they have for GWT and build them for Closure.