TurboLinks is going to be in Rails 4. That was well vetted :/
-
-
Replying to @johnbender
@johnbender Has@steveklabnik heard about your worries about how it’s going to screw up [push|pop]state?2 replies 0 retweets 0 likes -
Replying to @evanphx
@evanphx@steveklabnik frankly the size of the js is red flag given that support for this is in JQM is ver complex. Base tag support anyone?1 reply 0 retweets 0 likes -
Replying to @johnbender
@johnbender@steveklabnik Turbolinks feels like a kludge. Why can’t a browse do this just as fast as a normal anchor?2 replies 0 retweets 0 likes -
Replying to @evanphx
@evanphx@steveklabnik page refresh == expensive: JavaScript re-execution, cache checks/reqs, initial DOM tree creation, etc etc1 reply 0 retweets 0 likes -
Replying to @johnbender
@johnbender@steveklabnik But aren’t those exactly the things the turbolinks JS code has to do to display things properly?4 replies 0 retweets 0 likes
@evanphx @johnbender js parsing and execution, as well as css parsing and execution. my tests show this to be about 30% faster
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.