4 ms·
I like the idea, although I don't like that someone has to write this for a framework. I mean, ideally this would be built into browser in some way. Recompilin
by romaniv 14y ago
I like the idea, although I don't like that someone has to write this for a framework. I mean, ideally this would be built into browser in some way. Recompiling cached assets seems like a waste of resources. Even re-executing JavaScript on page load could be controlled via some link parameters or headers.
- FuzzyDunlop 14y agoIn terms of pushState, I think it is, and the framework only truly exists to abstract the differing implementations across browsers. But naturally, when a page is refreshed, the code has to be re-executed, because you're resetting state and performing all sorts of setup and initialisation. That being said, and I'm only putting this out there, but lisp-esque continuations in the browser for this sort of stuff? Also, part of me thinks that if you require this sort of thing, Rails is the wrong tool. Rails is great, but a full stack framework is pretty intensive for this sort of thing.
- jarin 14y agoI think the thing about turbolinks is you get a lot of the advantages of single-page apps but you can write it like a normal Rails app.