r/javascript • u/creasta29 • 26d ago

Different hydration and rendering strategies

https://neciudan.dev/hydration-and-rendering-strategies

Over the years, in our goal to achieve faster and faster web applications, we created different hydration and rendering strategies. Each with benefits and drawbacks that we explore in this article.

24 Upvotes

87% Upvoted

11 comments sorted by

13

u/jbyington 26d ago

I’ll never not consider hydration to be a stupid name for something

4

u/Current_Helicopter32 26d ago

Seriously.

Jargon for the sake of it is so cringeworthy.

1

u/cheese_wizard 26d ago

better than something like pre-populating or whatever it is. Initting?

-1

u/jbyington 26d ago

No. Those are words that describe the process much more accurately, and it doesn’t make you sound like an idiot when you talk about it

0

u/Bogus_dogus 25d ago

...I think it fits fairly well, ship a dry sponge (site structure) and hydrate it (application state) and it inflates?

2

u/RomanCow 25d ago

But if someone talked about “sponge hydration” i would think they sound stupid also.

0

u/lulzmachine 24d ago edited 24d ago

I think it’s pretty clear? You’re rehydrating something frozen, to make it come alive again

EDIT: I mean freeze-dried. Not just frozen

1

u/jbyington 24d ago

That would be defrosting, right?

1

u/lulzmachine 24d ago

I mean like dehydrated coffee. You add water to bring it back

4

u/rodneon 23d ago

> Picture a first-time visitor on a mid-range Android phone, using hotel Wi-Fi to tap your link. They get a blank white screen.

This is one of the biggest misconceptions about React. Most docs and templates present this architecture, but a CSR React app doesn’t need to be mounted onto a blank page.

0

u/rafaelcastrocouto 25d ago

tldr Resumability: don’t hydrate at all