The Story of Concurrent React

2,161 days. That's how long the React team has been working on this release. This video tells that story.

[tonytino]

Excellent work as always. Especially appreciated the love for Harambe. He's eternalized in the test suite of a code base I worked on for several years and will always hold a special place in my heart. 🖤 🦍

[rohitteja]

This is by far the simplest and best video I've seen on React 18. I'm now a fan!

[Kalazt]

Another video, another banger. Thank you for producing such high quality videos for us devs. Always pleasure to learn through these

[sle]

Continuously stunned at the level of research and quality put into these videos. Just absolutely incredible

[ritabest]

As always, excellent presentation! Thanks, Tylor, for taking the time - you always take these high-level concepts and break them into manageable, bite-sized, engaging content. I always learn something new and interesting.

[LaxMariappan]

Becoming a fan of your work Tyler. Glad to see your effort delivers quality output and also well received by devs!🔥

[saurabhprakash]

Glad that I discovered your channel. Thanks 🙏

[RasmusSchultz]

Five years invested in workarounds (mind you, not solutions) to problems inherent to the React model. The concurrency applies not to updating the DOM (which you can't do concurrently) but to all the extra work React has to do *before* updating the DOM. All this scheduling work accomplishes (if used correctly) is optimize *perceived* performance - but the framework is actually net slower than it was before doing this extra work. Meanwhile, other frameworks such as Solid, Svelte, Imba and others have moved on to a model that updates the DOM directly, instead of doing all this unnecessary work on an in-memory duplicate of the entire DOM, which has to be reconciled with the real DOM before doing actual DOM updates. React keeps adding layers of complexity to get around a fundamental design issue - and developers seem to have the perception that all this extra complexity is inherently necessary, and even ironically take pride in knowing how to apply all the new performance features to achieve acceptable performance. Meanwhile, other frameworks are moving on to much simpler models, where these performance features aren't even necessary in the first place. Regardless of how pointless this effort is, there's a market for it, there is job security, and so on - apparently that's the only thing governing the success of any framework in this industry today. 😕

[kohelet]

Coming from today's newsletter 😎 thank for this clear and really interesting video !

[WajuAbolarin]

Your content literally made me pause to check if I had subscribed, this is some top shelf content.

[shachi]

This made so many things clear! Thank You for your work. ✨

[espressothoughts]

Just found the channel. Had to subscribe.

Great work!

[walidn]

really great context about async rendering in React ! Really cool to have alternative apis for delaying user input (debouncing/throttling) user input like useDeferredValue

[SpaceGravy]

First time discovering this creator, liked, subscribed and commented. Nice job.

[AbdelhameedG]

Thank you, Tyler, quality content as usual.

[bahaarizk]

Wow man! Time to binge watch your content

[derockx]

First time seeing this channel, and I gotta say, the animation and quality is amazing! Keep up the good work!

[alexbrown]

It was smart that they went with the approach of concurrent "features", instead of an all or nothing concurrent "mode"

[Matt]

Great video and fantastic explanation, thanks heaps!

[zummotv]

Finally more people are viewing this amazing content .