| Chrome is light weight, unbloated, it's just one of the reasons why I'd say that it has excelled so quickly. When it starts supporting a tonne of libraries it has to really start beefing up on it's dependencies. So, at what point should Google allow/prevent access to their CDN. Additionally, the CDN is notoriously slow for updating to the latest versions. How would these changes them be rolled out to the browser? Through updates, or just realllly long caching? Plus, this would then turn into a kind of DMOZ, where libraries compete to get included and struggle... Plus the CDN supports multiple versions, does this mean that Chrome would have to support all 22 versions of jQuery? jQuery is not a defacto library. I don't start a project and immediately think, lets include jQuery. However if it was precompiled, in Chrome, then the barrier for making this choice would be lowered, and I might find myself just including it for the sake. I think this is totally unfair to other librariesm and it could quite possibly prevent or at least stifle innovation to some extent, since if the footprint of including jQuery in your application is zero, why not just include it, rather than try some other cool DOM project that's not included in the CDN. |
Chrome might be fast, chrome might be clean, but with its one process per tab model it will never be light weight.