I for one am in the "unwilling" category since I am stuck in IE7 for roboform and for some use of IE7 rich text editor mode. Chrome frame is what I need today. This is like Windows containing a DOS backward compatibility mode in the '90s - it's a transition path strategy. When rf supports Chrome browser and I have moved off my home grown rte WCM app (to Google sites), then I will switch. No Google, I will never store pwds in the browser, so get on the phone to rf pdq.
Not only does Google want Chrome Frame to make all apps work & simplify development. They are willing to hold success of their killer app (Wave) hostage to everyone either moving off IE, or at least going "half-way" to Chome Frame.
This gives them critical mass the fastest route. And they are smart enough to provide this as a developer platform since this it the other side of the coin.
Now let's see what happns when MS kills Chrome Frame with the next IE "security" update.