29 Feb '16, 2pm

Turbolinks vs the Virtual DOM

Turbolinks vs the Virtual DOM

On Friday, Nate Berkopec tweeted out: Side effect of the Turbolinks-enabled mobile app approach - guaranteed to be fast on old/low-spec devices b/c the Javascript is so simple. — @nateberkopec Think about the operational complexity of React versus Turbolinks. An entire virtual DOM versus "$('body').innerHTML(someAjaxResponse)". — @nateberkopec He justified his hypothesis by showing that the Ember TodoMVC takes 4x as long to update as a Turbolinks version , which I found odd because his original claim was about virtual DOMs, but the Ember TodoMVC uses an old version of Ember that doesn't use a virtual DOM — Ember's virtual DOM, called Glimmer, didn't appear until 2.0. It injects HTML, exactly what Turbolinks does. The only difference is that that HTML is generated by the browser. It trades a round trip to the server for CPU usage on the client. Having spent the last year or...

Full article: http://jgaskins.org/blog/2016/02/28/turbolinks-vs-the-vir...

Tweets

Turbolinks vs the Virtual DOM #reactjs #ruby #r...

linkplugapp.com 01 Mar '16, 2am

Receive Top ReactJS Content Weekly Join our free newsletter! skip

#Strings concatenation in Ruby (script provisio...

abizy.com 01 Mar '16, 3am

We do not share, store or cache any illegal files on this blog. We only share digital contents those are licensed under “C...

Benefits vs. Features: Understand the Differenc...

webmarketingtoday.com 29 Feb '16, 1am

If you want to increase your sales without investing more in driving new customers to your website, then you need to boost...

How to upgrade to Turbolinks 5

rubyflow.com 26 Feb '16, 3pm

× The Ruby and Rails community linklog Made a library? Written a blog post? Found a useful tutorial? Share it with the Rub...