News for hackers. Stuff that matters.
Re:React Concurrent Mode by jbaudanza on Thursday October 24, 2019 @04:57PM (#21349085)
OK I've spent all morning reading about this. I think that when you say "work", you're talking about the work of doing DOM updates. Rendering a VDOM is still considered cheap.
Re:React Concurrent Mode by joe_hoyle on Friday October 25, 2019 @04:09AM (#21352847)
The "work" is the arbitrary JavaScript in the `render()` function. In Concurrent mode, a `render()` function that renders 1000 children can now be interrupted "between" renders of all those children.

It's akin to doing `Header( LoginLink( GetLoginName() ) )` versus

``` Header(); check_for_interrupt(); LoginLink(); check_for_interrupt(); ... ```

The interrupt between rendering components (pieces of work) can now cancel the whole render operation (because say, the parent component has now been updated / wants to be re-rendered), or can pause the render tree while something like a high-priority animation frame is rendered.