Managing React Application State Management - Talk by Kent C. Dodds 

THIS is the big league stuff I like to submerse myself in! I had to comb through about 200 thumbnails covering "advanced" topics with class component based state counters. Def not helpful when you're looking for real talk like this. awesome job Kent, looking forward to one of your courses/workshops in the future!

I really appreciate the clear communication. This simplified a lot of issues that have been confusing me. Great teacher!

This was so good. I feel like it's really hard to find more intermediate to advanced stuff on react especially on youtube but this was great

So, I understand making things too complicated with global state. And I've really struggle to keep my state scope minimized and properly isolated. However IMO the best part of separating state (I haven't used redux much, but NGRX (redux for angular) and BLoC (similar idea in Flutter)) is that all of the logic is separated, state can be inspected at discrete steps and verified in testing, and the UI can be tested separately to make sure that it displays a given state correctly. This is the biggest strength IMO.

i love how this is added to the smiley videos playlist

Thanks, learned some useful things about React State

That was a great presentation. Thanks

Very insightful tutorial on React State. Thanks. {2022-03-14}

THanks a lot, brother

Thank you

This is great. It amazes me how people latched on to redux when it really isn’t necessary with modern react. When I hear redux the first thing that comes to mind is a black mass ceremony 😂

Very useful for me. Thanks.

Great talk 🎉

Thanks Kent! this is amazing

What a wonderful talk

Great tutorial and well explained!

Rather than creating a global context or having a page-level context, should we have Context.Provider wherever necessary in page component or its children, as long as the context lives in the closest common parent? Is it ok to sprinkle Context.Provider all over the component tree wherever necessary to try to colocate state?

Amazing!

Thank you very much! :)

What font was it? Didn't get the right one ig, and thank you for the video! Was much of help.

Why are we trying to cache our server data in javascript using complex state management libraries instead of just letting ETags and the built in cache control in the browser take care of this for us?

This composition thing seems like regenerating the same "global space" idea, just not in the state layer, but in the JSX layer. And prop drilling _is_ a problem, despite that it's not react specific, it still is a problem, it makes your components context sensitive. Prop drilling and JSX composition essentially carries the same kind of parameterization overhead issue. Any kind of overhead is a problem. It's much simpler to handle state orthogonally, in a separate, "global" layer.

Amazing. Does the React context has any performance issues when tol many contexts are used?

urls in description would be nice,

great talk

anytime you add time to anything

I don't like to lift the state up. The reason for that I believe it's not a good encapsulation. And make the component to which the state really belong to, make that component not reuseable.

Another solutions: Redux Toolkit (Modern Way).

Soo... is Redux dead?

Omg!

This ain't no smiley face...

Yo I thought it was C9 Perkz