Harambe was like father to me

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. 🖤 🦍

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

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

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.

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

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

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. 😕

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

Loving your content, keep it up!!

Glad that I discovered your channel. Thanks 🙏

Thank you, Tyler, quality content as usual.

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

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

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

your videos are very very very informative, thank you very much for explaining all these things brilliantly

Great videos, learning a lot.

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

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

The react team left us in Suspense!

Great video and fantastic explanation, thanks heaps!

Have to subscribe immediately after watching your video. Appreciated

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

one of the best channels. keep going.

Just found the channel. Had to subscribe. Great work!

Wow man! Time to binge watch your content

Thanks for the awesome content

This video made me subscribe. Wonder how i haven't stumbled on the channel before

Loved the video Tyler, keep it up.

Its scary how small this channel is. Keep the awsome work man ❤️🔥

RIP Harambe

awesome high quality content. I'm surprised why you don't have millions of subscribers yet :D

lovinng the content

This was so helpful, thank you! I still have one niggle: Your Suspense example conflated empty state and loading state.

Beautiful tribute to Harambe. RIP

Actually I am new to React. I didn't get much of the things but liked your presentation style and teaching style.

Finally more people are viewing this amazing content .

Really great content!

Great work 👏

I wish Harambe was still around to see React 18 😭

Awesome video!

Great content; subscribed

Terms low level and high level are so confusing in inherently high level ecosystems.

What I found fascinating about this is how much preparation work and things in advance they had to do in order to get to here. It's not something that was decided and done in 6-12months. It took years, it's crazy.

Great content ty.

I love these kind of videos . Do it for more technologies

The quality of these videos is unbelievable

Great explanation :)

One day React is going to be awesome...

Over the years, it's easy to loose track of context. This video sums up.

What a great video 🤍🤍

Wow impressive video. You have my sub :)

Great video

2 thousand freaking days! For something that we probably don't need, for a library that will probably be replaced in the next 3 years.

Hey! Nice video. What tool do you use to animate these videos ? :)

It's a great explanation I've ever seen , I've been struggling to understand Suspense and useTransition hook ;)

Great video. What font is that on your headlines? Very modern and clean, yet interesting font

Great presentation

Beautiful video i love it 💕

These story videos are amazing ✨. Please cover vue/nuxt as well.

I've done this on our corporate's multi user client management/invoicing/payroll system for like 10 years now. I guess it's about time, maybe one day these things will be usable instead of me having to make everything myself. RIP harambe

Great video, thanks. what do you think about the future of Svelte (Sveltekit)

Great video! What do you use to edit?

One more reason why they did not go with the service workers is the expensive context switch to perform the task. In case of state calculations it becomes even more evident and obvious to not use workers.

brilliant

I got more knowledge about react in one video than my first year of using react..

That's one one giant small step for leap for mankind. man,

Man I wish my boy Harambe was here to witness this updatw

It's still a bit unclear whether upgrading to React 18 is a good idea yet; especially if you are using Next (e.g. Suspense is discouraged for data fetching). Would be great to get your ideas on this Tyler? Thanks

useId seems useful, I've been passing down uuid to generate unique ids for form input for a while now.

Badia h

Great video, didn't understand a thing, but great video nonetheless.

I'm still really confused on Suspense. How do I tell react that a component in Suspense's children is not ready yet?

When is the server side components coming . ..?

Another excellent video on how ill-conceived react is. A never-ending trail of fixes disguised as features.

Long live react

We is this so high quality dammit!? we don't deserve this kind of good quality lol

great content 👏👏 keep it up !!

In the input and list example you gave, how's using the new concurrent mode different from debouncing the rendering of the list on input change, as far as visual rendering performance is concerned?

The next course will be on react query I guess?? 👀

Hi. Can you do npm vs yarn? or something like that.

"We're in the endgame now"

useDeferredValue is debounce an alternative? It's a little confusing as a beginner

It is and always will be too soon 🖤🦍

Will you be updating your courseware to React 18?

"this is not a performance problem, this is fundamentally a scheduling problem" Keep telling yourself that 😅

He got my undivided attention when he said harambe was alive

So for now we kind of "opt in" to these Concurrent Features on case-by-case bases in the same manner we would identify a complex situation that calls for Memoization?

Ah, Papyrus font in the outro. Trolling UI people, I see...

Sorry, but I don’t get it. I’ve never come across an instance where I would need this (I think). Do you maybe have some real world example of where this would be absolutely necessary?

3 years ago I decided to do more front-end work and learned react, hooks where the way to go. Went on a couple interviews and they cut me dry because their codebase was still in older react versions and I couldn't use hooks. I learned from an old colleague same shit went on with Vue. Frameworks where chaning too fast for the corporate world to adopt and new releases were considered unstable bacause custom components getting incompatible... I got so frustrated I devoted to Svelte, new kid in the block but simple AF. Long story short my components from 2019 still work on latest svelte and I can inject them in any webpage, no matter what framework it uses. Best choise I've ever made.

Harambe was alive haha oh starting it off with a heart breaker

I love u

how do you make animations like this?

Ooooor you could make rendering the list less expensive by building a faster VDOM or just not using one in the first place ;^)

as a person who just started learning react i have no idea what this video is about :")

So React is finally catching up with what Angular has been able to do out of the box for years now? Am I missing something?

Should be little project with all new features

now that concurent is here. what's next in line?

Remix video maybe? Or vue?