I hadn't heard of Chrome Frame until this discussion, but the basic suggestions at http://code.google.com/chrome/chromeframe/ sound a lot like "This page best viewed in $BROWSER at $RESOLUTION". Didn't we learn that lesson yet?
> Google I/O 2011 - http://www.google.com/events/io/2011/sessions/html5-today-wi...
> Google I/O 2010 - http://www.google.com/events/io/2010/sessions/using-chrome-f...
"at least they make it reasonably straightforward for sysadmins to manage policies across a whole workplace."
> Google recently came up Administrative templates for Chrome. But I wonder why they didn't push it enough to IT departments - http://www.google.com/support/installer/bin/answer.py?answer...
In any case, there is something very shady about the whole project. If people want to use Chrome, let them use Chrome, but please let's not start making IE pretend it's Chrome (or was it the other way around?). How on earth are corporate IT support people supposed to deal with requests for help from non-technical people once we start down that path?
Just asking if it works well.
[1] http://code.google.com/p/chromium/issues/list?can=2&q=la...