And here I thought this was a post about the google.com source code being leaked. :-)
I'd imagine that the rendered HTML is probably produced by a legacy system that stitches together a lot of different templates, some maybe even unintentionally.
I wonder why there are multiple style elements, in div#footcnt there are 2 right next to each other, they could have saved a whole "</style><style>" there, think of the bandwidth!
I'd believe it. As someone else mentioned above, they've also started inlining image data, so I wouldn't be surprised if these changes all fell under the goal of minimizing HTTP requests.
The other day I noticed that they're inlining image data in the src attribute instead of pointing at an external URL. Really taking things to the next level all-around - I wonder when that will become the norm instead of css image sprites.
Hopefully never, and certainly not with http 2.0 around the corner (this adoption wont be so slow, things are already starting to fall neatly into place). It's a micro-optimization Google can afford to do, others will just rely on optimize images size and a CDN instead (possibly an extra hostname) and vast majority wont/don't even bother..
