4 ms·
Compatibility aside, how in the world can fetching a page then rendering it be faster than “a full page load”? That’s the definition of a full page load! Are we
by twhb 9y ago
Compatibility aside, how in the world can fetching a page then rendering it be faster than “a full page load”? That’s the definition of a full page load! Are we assuming heavy JS in the <head>, and that it’s also present on the current page?
- ravenstine 9y agoI haven't touched Turbolinks since the the first version(at one point there was a rewrite if I recall), but I'm pretty sure it would only replace the body and not reinsert the head content, thus meaning that the existing scripts continue to run without being "rebooted" or downloaded again. Plus there's a slight benefit from not building a new DOM. The downside is that all your scripts can't depend directly on 'DOMContentLoaded' or jQuery.ready. This isn't much of a problem if you're using a framework where navigation is abstracted away anyway, but third-party software can still get messed up. I was surprised that the extension didn't interfere with my Ember.js app, but then disappointed when it prevented Leaflet from working across navigations. I honestly don't know why that would be the case since my app already does its own navigation without page reloads.