HackerTubewatch
Surprise me
Frame from Dan Abramov: Beyond React 16 | JSConf Iceland Plays via YouTube's privacy-enhanced embed

Dan Abramov: Beyond React 16 | JSConf Iceland

13 videos recommended on HN
YouTube
3 HN users recommended this talk3 months2018–2022 score 3.5
Years with an HN recommendation, 2007–2026

Recommended as the clearest demo of what concurrent rendering solves, including the memorable clock animation.

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.

“That clock animation is pure genius” (HN, 2019)

1 strong recommendations · 2 recommendations · 2 citations · Talks · intermediate · partly dated

5 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@throwaway_bad Oct 2019 Strongly recommends
on HN thread React Concurrent Mode
The clearest demo that communicates what this solves was given when it was announced last year. That clock animation is pure genius: [this video]
Clearest demo of what concurrent rendering solves
@ggreer Oct 2018 Recommends
on HN thread Introducing Hooks
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]
Live coding demo of future React features like asynchronous rendering

Citations, criticism and jokes

@mlsarecmg Sep 2020 Cites it
on HN thread React is becoming a black box
Read more
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.
Demo illustrating concurrent mode scheduling and prioritizing user input over lesser work.
@herrkanin Mar 2022 Cites it
on HN thread React v18.0
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]
Early showcase of React concurrent features by Dan Abramov.

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close