Google didn't have a choice about Chrome Frame. The new Internet Explorer 10 doesn't support plugins that are as invasive as Chrome Frame. See http://msdn.mic

Google didn't have a choice about Chrome Frame. The new Internet Explorer 10 doesn't support plugins that are as invasive as Chrome Frame. See http://msdn.microsoft.com/en-us/library/ie/hh968248%28v=vs.85%29.aspx http://msdn.microsoft.com/en-us/library/ie/hh968248%28v=vs.8... Chrome Frame on older Internet Explorer versions shouldn't really need to be updated that much, since those browsers aren't changing that much. Also, I find it really hard to believe that the kind of IT department that decrees that everyone has to use IE6 (or whatever) would ever allow such an invasive third-party plugin as Chrome Frame in the first place. The limited browser compatibility of dart.js is a real issue and probably is a dealbreaker for some enterprise situations. But there's no need to bring Google Reader into this-- it has literally nothing to do with it. The other thing which everyone seems to be missing here is that even if Google does "become bored with Dart," there will still be an open source community to support it. Coffeescript has been around forever without any sugar daddy. A big part of the reason for using open source technologies is to avoid vendor lock-in and other similar questions about the future.