Why does Zustand use the term “hydrate” when syncing data from storage back into state?

[ByungyeonKim]

Hi, I've been studying the persist middleware and noticed that Zustand uses the term "hydrate" (and "rehydrate" in onRehydrateStorage) to describe restoring state from storage back into memory.

While I understand the conceptual similarity to Next.js's hydration—both involve "breathing life" into inactive data—I'm curious about the design decision behind this terminology choice, and if there is a specific conceptual reason behind the term.

Would appreciate any insights into the reasoning behind this terminology decision, or if there were alternative names considered during Zustand's development.

Thanks!

[dai-shi]

I'm not sure but it's probably hydrating SSR vs. hydrating storage (memory).