@vaporeon_ https://en.wikipedia.org/wiki/Hydration_(web_development)

@wallhackio Whoever came up with that word is ultra reported in the name of all water-type Pokémon

@vaporeon_ @wallhackio when loading a webpage from a site developed in react in such a way that it uses what they call “server-side rendering” (SSR), you initially receive a page in an intermediary stage where the HTML is rendered. (befur SSR was the norm, client side JS was fully responsible fur rendering the entirety of the HTML on the page.) “hydration” refurs to the effect of loading extra JS to load the react runtime into the client, so that the page can do all the interactivity and client side rendering and client side routing expected of a react-based website

@vaporeon_ @wallhackio this is not limited to react

@aescling @wallhackio JavaScript web frameworks are an abomination

@vaporeon_ @wallhackio i agree

@aescling @vaporeon_ it just seems like something that should have always been there in the first place

@wallhackio @aescling None of this should exist and JavaScript shouldn't exist

@vaporeon_ @aescling reported

@aescling @wallhackio I am also having trouble parsing the original question.

@aschmitz @aescling @wallhackio i think the idea is like, does it basically just amount to having a web app that performs queries and generates responses old style, like how things were pre SPA or even pervasive JS

@aschmitz @aescling I would imagine in 2005 that having a server serve HTML that has some JavaScript loaded afterwards that adds interactivity would just be, like, the obvious way to do things

@wallhackio @aescling Ah! Uh. Kind of. Early JS-based progressive enhancement (if you were lucky) tended to rely on existing HTML or inlined data. Hydration is kind of inlined data, but the main difference there is that a SPA that can be hydrated is almost certainly running [nearly] the same code on the client side as was on the server side to generate the page served directly, so you're basically bootstrapping a client-side version of the site, rather than adding JS to a server-side thing.