4 ms·
the newly recommended library, redux, is great. Flummox was great too, but redux is better, I recommend giving it a shot if you haven't. To the original point,
by betenoire 11y ago
the newly recommended library, redux, is great. Flummox was great too, but redux is better, I recommend giving it a shot if you haven't.
To the original point, you are still sending the data twice, once in rendered html, and once in that state that gets rehydrated.
- Ambroos 11y agoDepending on the kind of content t you have, that's hardly an issue. I've built a big site like this, and gzip does an extremely good job at filtering out duplicate data. Check the source of http://viva.vlaanderen/ http://viva.vlaanderen/
- betenoire 11y agowhen you view the source of your page, you see that very little of the dehydrated state is used to build your initial markup. The entire rendered source is 142K. I isolated the actual markup, and it weighs in at 31K. In other words, your dehydrated state is 4x bigger than your html rendering. And that's not including your 750K main.js file that also gets downloaded. That's almost 1MB of downloads (not including images and stylesheets) just to "app-ify" your 31K of markup. I tend to agree, it's not a problem. Or perhaps, it's not one of the biggest problems. But it's not "hardly an issue" either.