“That clock animation is pure genius”
Clearest demo of what concurrent rendering solves
Full comment
The clearest demo that communicates what this solves was given when it was announced last year. That clock animation is pure genius: this video
Dan Abramov: Beyond React 16 | JSConf Iceland
139K views · Apr 5, 2018 · 33:25 · 3 HN recommenders · 5 mentions · discussed 2018–2022
Dan Abramov's JSConf Iceland talk on what came after React 16, with live-coded prototypes of async rendering and time slicing. It previews the ideas that became concurrent mode and suspense.
Why Hacker News points people here: Recommended as the clearest demo of what concurrent rendering solves, including the memorable clock animation.
“That clock animation is pure genius”HN comment, 2019
What Hacker News said 5
“If you like live coding demos, he also gave a talk at JSConf Iceland”
Live coding demo of future React features like asynchronous rendering
Full comment
Dan Abramov's talk starts 39 minutes into the livestream: link If you like live coding demos, he also gave a talk at JSConf Iceland where he showed off some future React features, such as asynchronous rendering: this video
“Watch this, it explains it in detail”
Detailed explanation of how React concurrent rendering scales with device capabilities.
Full comment
Yes, but it scales with the environment and device capabilities. Watch this, it explains it in detail: this video
“This demo illustrates the issue”
Demo illustrating concurrent mode scheduling and prioritizing user input over lesser work.
Full comment
These apps all fall flat, which is the point i'm trying to make. They're robust from a design perspective, the tools we have to build UI are good enough, but they can't compete against native. Do you think that using Svelte in any those would make a difference? This is why React is attempting to find a solution. The problem is essentially the same. Native apps are also conflicted with load, they have better means than we have on the web to deal with it, but it's still low-level and complex to orchestrate, threading for instance. Any one of those means pushes your app into async issuee, race conditions that you need to reconcile. With concurrent mode scheduling is a first class concept , your components won't be subject to race conditions. React maintains 60fps, high-priority content (user input, animations, transitions) can be ran fluidly while lesser priority content gets deferred. It has a good chance of outperforming multithreaded native apps with that model. This demo illustrates the issue: this video which is universal. You run into this on native platforms as well as on the web.
“I remember three years ago when Dan first showcased some of the concurrent features”
Early showcase of React concurrent features by Dan Abramov.
Full comment
Congratulations to the React team! I remember three years ago when Dan first showcased some of the concurrent features [1], so this has been quite long in the making. [1] this video