Summary of You still use Redux?

00:00:00 - 00:35:00

In this video, the presenter discusses the benefits and drawbacks of using Redux. They note that Redux can have side effects, so they have to be careful about how they modify the state. They also mention that using mutations (instead of using an event handling system) can make code more bug-prone. They end the talk by recommending using a query client to invalidate queries instead of revalidating them every time they change the state.

• 00:00:00 In this video, the speaker explains the different types of state in an application and why they're important. They then discuss state in relation to React Query, which is a powerful tool for synchronizing a server with a client.
• 00:05:00 In this video, the presenter discusses how application state and server state are different, and how the default state should be server state. They also talk about how to ensure that the state is always loaded from the server.
• 00:10:00 In this talk, the speaker discusses the benefits and drawbacks of using Redux. They note that Redux can have side effects, so they have to be careful about how they modify the state. They also mention that using mutations (instead of using an event handling system) can make code more bug-prone. They end the talk by recommending using a query client to invalidate queries instead of revalidating them every time they change the state.
• 00:15:00 In this video, the presenter discusses how they use React Query to interface with APIs. They explain that there are various ways to do this, and that the most common solution is to use React Query to update variables based on successful API requests. They also show how to use optimistic updates to make changes even if the API returns errors.
• 00:20:00 In this video, the presenter discusses how Redux can be useful for certain things, but is not the best solution for other applications. He recommends using built-in React state, prop drilling, or context for dependency injection where necessary.
• 00:25:00 Redux is a state management library that can be used in React applications. However, there are times when it might not work well for a certain user. Jodi is a state manager that is fantastic for ergonomically pleasant state management. It has a system called atoms that allows for simple, atomic state management.
• 00:30:00 The main points of this video are that jodi is simpler, better maintained, and more likely to keep doing well, while recoil is similar but simpler and better suited for less complex state needs. Jodi and zestand can be used together to solve specific problems that React's built-in state library wasn't built to solve. X State is a more formal state machine architecture, but it can be useful for complex state needs, but should only be used if you have a lot of complexity in your state. Trash mentioned in the chat that he likes x state, but it falls apart when sibling machines need to communicate.
• 00:35:00 The author of the video talks about how they use Redux and how it works. He then talks about how he uses other systems to solve problems that Redux can't. He says that it's a good system, but that there are other systems that are simpler and that are better for certain cases. He finishes the video by saying that if you're not already watching his videos, you should go to Twitch and watch them live.