QUOTE(jimlongo @ Sep 24 2009, 12:41 PM)

Maybe there's someone around here who works at Google

and knows something.
It turns out that Google is a big place, and I don't work on anything related to Chrome or Chrome Frame. And even if I knew something, I wouldn't be able to discuss it.
But speaking as a web author (and definitely NOT speaking as a Google employee):
I like the idea of being able to include
CODE
<meta http-equiv="X-UA-Compatible" content="chrome=1">
to switch MSIE from the Trident rendering engine (which I can't test without a copy of MS Windows) to the WebKit rendering engine (which I can test on Mac/Linux). Sure, those without the Chrome Frame plug-in will be stuck with Trident, but those with the plug-in will be able to use WebKit.
As for prompting the user to download the plug-in, I think it depends on the situation. If your content needs HTML 5 features that MSIE doesn't support without Chrome Frame, then I don't see this as any different from prompting the user to install/enable Flash, or to enable JavaScript, or to enable cookies, or to enable anything else. If your content needs these features, then go ahead and prompt. Or if your content doesn't need these features, then go ahead and offer an informational link, without forcing anyone to download anything.
On the other hand, I don't like "use my preferred browser or else" campaigns, even when they're promoting one of the browsers I happen to use.