4 ms·

Chrome Feature Request: Include commonly used JS libraries directly in browser

• btilly 16y ago
  Wonderful. And then when a tweak is needed to said libraries, you have to upgrade the browser to correctly render the web page? Let's not.
  • frombz 16y ago
    If the library doesn't exist locally in the browser, the page will load in the same way it loads today (and in browsers that don't support this). Because the feature would only replace known (and working) URLs with a local copy, it's backwards compatible and would continue to work with new versions of the various libraries.
  • devicenull 16y ago
    Chrome already does transparent updates to the browser, it's doubtful you would even notice that. But they are talking about a very limited application, only replacing the libraries where they know the exact version ahead of time (only the one's on Google's CDN). I would assume if the browser doesn't recognize a library, it just falls back to downloading it from the website.
• rlpb 16y ago
  The first time the page is hit, the browser should keep it cached for a year. How much time will avoiding that first hit actually save? Keeping a file compiled could be more generic too: just check which URLs get hit a lot, and keep those pre-compiled as a separate feature.