
🖼️ Next.js: Open Graph Images
Generate dynamic images in your Next.js projects for sharing on social media.
💸 First lesson available without registration 💸
This course will help understand the implications of the changes that have occurred in recent years regarding state management in SPA applications with React, whether someone is already familiar with React or has just started working with it in recent years.
The React ecosystem since its creation in 2013 has been particularly dynamic concerning state management, and, with such a non-"opinionated" framework, various alternatives have emerged with varying degrees of success.
At least one thing is clear: Redux (released in 2015) has marked a turning point in state management. In fact, it remains one of the most widely used solutions today and is prominently featured in courses and available literature.
With the emergence of Redux, we shifted from very basic and handcrafted state management with setState to something entirely different, where all the application state resides in a central store, and changes or mutations to that state are specified declaratively.
As with almost everything in technology, swinging from one extreme to another tends to leave us with a middle ground where, after evaluating several tradeoffs, we find a reasonable balance between complexity and functionality.
During the course, we will examine these tradeoffs to better understand existing solutions and thus decide which is the most suitable for each use case.
Starting from basic state management with React, we will look at Redux in its traditional form and analyze what alternatives the ecosystem offers to achieve the same objectives without as much complexity:
We won’t increase the price while your subscription is active