Google has done the bare minimum to show what their cool engines and architecture can do. The main contribution Google's Chrome brings to the table is the stuff Under the Hood (TM). This is primarily a software engineering innovation that has spill-over benefits to us as designers, just as a "doubled frontside data bus" or "predictive branch optimization" enables us to do more, even though most of us don't really care how it works.
Chrome strikes me as a "reference implementation" that browser vendors, engineers, and designers alike can use to evaluate the underlying technologies and see if they make sense for integrating into their apps (Browsers, desktop apps, Web APIs, etc). Further, each of these innovations is a bandaid on a much larger problem-- web browsers were never intended to do the things we do with RIAs. And maybe this is a bit off-topic and troll-worthy, but speaking as a software engineer (past life), AJAX is a series of hacks. Perhaps we can take Chrome's V8 engine, process management, and malware/spyware thwarting in the interim to pacify ourselves while we wait for the shakeout of a robust, cross-platform, high performance toolkit un-messed with by your evil empire of choice. All Pollyanna-like, - Nasir ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
