halting that users see […] Jank is the result of frames taking too long for a browser to make, and it negatively impacts your users and how they experience your site or app.” — jankfree.org #MelbJS March 11, 2015 — @plasticine 4
a scathing condemnation of the DOM/CSS web standards stack.” — John Gruber 2 2 http://daringfireball.net/linked/2015/02/10/flipboard-web #MelbJS March 11, 2015 — @plasticine 6
is akin to calling a collection of tires, AA batteries and spare car parts a Tesla.” — Faruk Ateş3 3 http://farukat.es/journal/2015/02/708-how-flipboard-chose-form-over-function-their-web-version #MelbJS March 11, 2015 — @plasticine 7
be scathingly condemned, while ignoring the enormous and extraordinary achievement of the technologies underlying the Web” — John Allsopp 4 4 http://www.webdirections.org/blog/60fps-new-image-replacement-technique/ #MelbJS March 11, 2015 — @plasticine 8
forget about all of that junk and pretend for the moment that this is a good idea, we’ll have more fun that way. :) #MelbJS March 11, 2015 — @plasticine 9
element —It’s content exists outside of the DOM —Draw stuff via scripting (Javascript usually) <canvas></canvas> <!— I’m an image, kinda, sorta. —> #MelbJS March 11, 2015 — @plasticine 10
data into a <canvas> context, instead of the DOM. Brings many of the architectural wins of React (composition, data-flow, etc) to canvas rendering. #MelbJS March 11, 2015 — @plasticine 11
performance (unlike native). No control over when GC happens (unlike native). Touch latency / gesture recognisers not as good. #MelbJS March 11, 2015 — @plasticine 27