If you develop applications in React, you've probably encountered the issue of hydration. The bright side of this process is that our application, initially rendered on the server side, becomes interactive. Until recently, hydration had to be done in an ''all-or-nothing'' mode. It was not possible to divide the process into smaller phases or turn it off completely for certain elements of our site, and we unfortunately had to suffer the consequences of this - i.e. sending more source code to browsers or using more or less elegant hacks.

Fortunately, the situation has changed, and the latest version of React has introduced some changes in this field. Hydration can now be split into stages and even prioritised. Better still, thanks to React Server Components, we can avoid it altogether and not send part of the code to the client! And what do the frameworks offer on this topic? Surprisingly much. Each of them approaches this topic slightly differently and allows us to use the aforementioned novelties in a different way.

If you are curious and want to find out:
- how exactly does hydration work?
- how you can tweak the hydration process?
- what are the advantages and disadvantages of selective hydration?
- what does its use look like in the latest frameworks?
then I invite you to listen to this lecture.

dev.js Summit 2023, 4Developers Łódź