æʃliŋ, loaf of autismo @aescling@cat.family

@vaporeon_ look at them go

@vaporeon_ @wallhackio por que no los dos

@vaporeon_ umbre

@vaporeon_ @wallhackio that’s the name of McYeehaw’s steed (McYeehaw rides a Clodsire)

@onfy did you think i said “noses”?

umbreon noises

also, mornyawn . @clock, do your thing

epic rap battles of history!

gayest plant

versus!

gayest zombieeeeeeeeeeeeeee!

begin!

@coriander …, goal-bin

@coriander sleep well

@vaporeon_ eh, design is impurrtant

@wallhackio @vaporeon_ squarder-cat was too funny to not vote fur

@vaporeon_ @wallhackio i agree

@vaporeon_ @wallhackio this is not limited to react

@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

@wallhackio reinventing the wheel in what way? which is to say, what exactly are you asking? (i almost certainly do not know the answer but i want to know what i want to try to figure out)