throwaway_badOct 2019Strongly recommends
The clearest demo that communicates what this solves was given when it was announced last year. That clock animation is pure genius: ▶ this video
in “React Concurrent Mode” · View on HN
Dan Abramov: Beyond React 16 | JSConf Iceland
Dan Abramov: Beyond React 16 | JSConf Iceland on HackerTube: recommended by 3 Hacker News commenters across 3 separate months, 2018–2022.
JSConf
Open on YouTubetalk · intermediate · dated
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 recommends it
Recommended as the clearest demo of what concurrent rendering solves, including the memorable clock animation.
- people recommended it
- 3
- separate months
- 3
- strong recommendations
- 1
- discussed on HN
- 2018–2022
“That clock animation is pure genius”
What HN commenters said
5 Hacker News comments link this video. Each one links back to its thread.
mlsarecmgNov 2019Recommends
Yes, but it scales with the environment and device capabilities. Watch this, it explains it in detail: ▶ this video
in “React in concurrent mode: 2000 state-connected comps re-rendered at 60FPS” · View on HN
ggreerOct 2018Recommends
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
in “Introducing Hooks” · View on HN
herrkaninMar 2022Cites it
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
in “React v18.0” · View on HN
mlsarecmgSep 2020Cites it
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.
in “React is becoming a black box” · View on HN