Too Long; Didn't Read
This article continues my series chronicling my investigation into <a href="https://hackernoon.com/tagged/javascript" target="_blank">JavaScript</a> performance by creating <a href="http://heapviz.com" target="_blank">HeapViz</a>, a visualization <a href="https://hackernoon.com/tagged/tool" target="_blank">tool</a> for Chrome memory profiles. Today I will be talking about my experience creating a <a href="http://jankfree.org/" target="_blank">jank-free UI</a> by using web workers. If you missed it, check out <a href="https://hackernoon.com/a-tale-of-javascript-performance-61c282f89f2a" target="_blank">part 1</a>, <a href="https://medium.com/@tomlagier/a-tale-of-javascript-performance-6011615523e8" target="_blank">part 2</a>, and <a href="https://medium.com/@tomlagier/a-tale-of-javascript-performance-8c4036f479a8" target="_blank">part 3</a>.