News for hackers. Stuff that matters.

A comment on The Path to Parallel JavaScript. Parent comment

Re:The Path to Parallel JavaScript by coderzach on Thursday February 26, 2015 @04:57PM (#9115825)
Anecdotally, I've found that most performance hick-ups don't come from computation blocking the ui, but from rendering one part of the ui blocking every other part from rendering.

The solution to that being parallel or async paint/layout, which is something I never hear mentioned (probably because it's a really hard problem).

[ Parent | on HN ]
Re:The Path to Parallel JavaScript by Joe8Bit on Thursday February 26, 2015 @05:20PM (#9115968)
Servo is actually in the process of implementing a parallel layout engine[1][2]

1: http://en.wikipedia.org/wiki/Servo_(layout_engine) 2: http://pcwalton.github.io/blog/2014/02/25/revamped-parallel-...

[ Parent | on HN ]
Re:The Path to Parallel JavaScript by kibwen on Thursday February 26, 2015 @05:39PM (#9116068)
They've recently landed a tool that makes it possible to visualize the parallel rendering: https://github.com/servo/servo/pull/4969
[ Parent | on HN ]
Re:The Path to Parallel JavaScript by amelius on Thursday February 26, 2015 @05:32PM (#9116021)
Interesting. I wonder how they handle incremental rendering though. Only the forward-path is described in your reference [2].
[ Parent | on HN ]
Re:The Path to Parallel JavaScript by sanxiyn on Thursday February 26, 2015 @06:18PM (#9116246)
As far as I can tell there is nothing unusual or difficult here. Servo's incremental layout implementation is here: https://github.com/servo/servo/blob/master/components/layout...
[ Parent | on HN ]
Re:The Path to Parallel JavaScript by idbentley on Thursday February 26, 2015 @05:21PM (#9115975)
I believe that the Servo project (https://github.com/servo/servo) is attempting to address exactly this.
[ Parent | on HN ]