Well, if you used microdata, you have an easy migration path, and if you used some other syntax, you don't. You can call that whatever you like, but it doesn't change the facts.
This is essentially everything I would have said on the subject. Python 3 is technically very good, but no one is using it, hence no commercial interest in the book. The optimist would say it was just ahead of its time. The pessimist would say Python 3 is a dead end and I backed the wrong horse. I'd say the jury is still out.
Interesting deductions! I just wanted to pipe in here to confirm that your math and your stated assumptions are correct. My take is the standard 10%. My "top tier" status, as you flatteringly put it, bought me the freedom to simultaneously publish the book online under a Creative Commons Attribution license. I negotiated for licensing, not money. I have no regrets.
Here's the story about the name: I wrote http://diveintomark.org/archives/2010/01/29/tinkerers-sunset earlier this year, decrying the lack of "tinkerability" of the iPad and similar closed devices. "There won't ever be a MacsBug for the iPad. There won't be a ResEdit, or a Copy ][+ sector editor, or an iPad Peeks & Pokes Chart."
One of the common refrains in the comments was that the iPad includes top-of-the-line support for a perfectly open, tinkerable platform: the web. Thus, the "HTML5 Peeks, Pokes and Pointers" chart was born.
Also, I just purchased a real live physical original Beagle Bros "Peeks, Pokes and Pointers" chart to hang up in my mancave^Woffice. Next to my Apple //es. Plural. So there's that.
I (the author) would agree with this statement, except for the baffling fact that Google Chrome Frame has a non-zero number of users. So obviously some people thought "I don't want a new browser, but I'd be OK with installing this plugin."
My build scripts are such an "evolved" mish-mash of Python3, Python2, Java, makefiles, and shell scripts that I'm amazed they work for me, much less for anyone else. (This point was brought home to me when I moved to a new laptop and spent too long trying to remember and install all the dependencies.)
Anyway, nice job, and hooray for unintended uses of open source code.
Ah, the oddities of CSS. The first issue is because I'm using custom fonts via @font-face. Firefox has made some... design decisions... that cause the effect you're seeing. I've actually just recently discovered a way to reduce the number of dynamic fonts I'm loading, but the underlying issue is still that Firefox wants to paint the page before the dynamic fonts are finished loading.
The second issue is CSS generated content. I honestly don't remember why I chose to put chapter numbers and appendix letters in CSS and the rest of the title in content. Purity? Really? That doesn't sound like me. ;-) It would probably be simpler to move it all into the h1.
My longer chapter on detecting HTML5 features ( http://diveintohtml5.org/detect.html ) explains the detection patterns, and shows how to detect things with or without Modernizr. I've been working with the Modernizr developers to expand their detections, and at the same time some of the code in this guide is taken directly from Modernizr.
This is a huge part of Android that, IMO, doesn't get enough press. On the iPhone, an "app" is a silo. You run it, it takes over, you go back to the home screen, it stops (modulo some limited background processing in iOS 4).
On Android, an "app" can be seamlessly integrated into the entire system. Think "extension" in classic Mac OS. My first experience with this in Android was "Rings Extended," one of the first apps in the market. It can (at your option) COMPLETELY REPLACE the ringtone selector, system-wide. Other "apps" can completely replace the home screen (OpenHome, aHome were two early examples). Other "apps" can complete replace the system-wide keyboard.
[disclaimer: I work for Google but not on Android stuff. My experience on Android is 100% based on phones my employer gave me for free.]
You don't read the news much, do you? ;)