Sax Maniac's Journal: Android Developer Documentation

I just got a G1 thanks to my lovely wife, and I continue to be impressed by it. But the most shocking thing so far is the documentation. Here's a choice quote:

If your application needs to perform some expensive or long-running computation, you should probably move it to a thread. This will prevent the dreaded "Application Not Responding" dialog from being displayed to the user, with the ultimate result being the fiery demise of your application.

First, that's some damn good writing, and is the polar opposite of anything on MSDN. Techincal, clear, not wordy, and not too serious.

Not only that, but check out the website. How fast it is, the distinct lack of corporate frills that plagues most technical documentation. How amazing, I click a link and I see the text without waiting 5 seconds for some awful Java tree control to load, scroll my page randomly around, change the font, only to show the topic I want nested eight levels deep in some documentation set inside of some piece of useless corporate foofery like HP Solutions Center > HP DeveloperWorks > Documentation > 2008 > Alpha > AdminiTRACK 2.3 > Developer's Guide > Localization Handbook > Estonian > Command Line Reference.

I learned more about Android in 5 minutes of fun reading, than I have in untold months paging through Microsoft's or HP's documentation.

Google is going to take over the entire tech world at this rate.