3 ms·
It serves div soup rather than modern HTML5. I am a stuck record on this topic but I think your document structure needs to come first. Simplicity always trumps
by Theodores 8y ago
It serves div soup rather than modern HTML5. I am a stuck record on this topic but I think your document structure needs to come first. Simplicity always trumps complexity when it comes to speed, no matter what the discipline.
- zamadatix 8y agoDoes it matter what it serves considering it's written in something completely different and the output is generated by a server not a human?
- 5Qn8mNbc2FNCiVV 8y agoAre you both stupid? He literally just hydrates his React application to HTML. If he wanted to not have a div soup he could have changed how its rendered. His output is 100% dependant on his input. Garbage in Garbage out thats how it is. Only thing thats cool about this is that its cached which should be standard anyways and then prefetches content on the page. And even then cool may be too much to compliment this with.
- Theodores 8y agoYes if the benchmark is speed. The new browser layout engines are quicker than the old floats and divs with billions of class tags. Plus the quickest download is always no download. Then there is the matter of maintaining the content. Div soup has to get chucked down the drain for the new agency or developer to make more div soup. It is worthless. Meanwhile, a document with proper markup and judicious use of semantic HTML5 tags is content with value that can be easily re-styled. SEO matters too, pure speed matters but so does document structure. Hiding your content in div soup does not impress the Googlebot. Next?
- dangerface 8y ago> The new browser layout engines are quicker than the old floats and divs with billions of class tags. Can you back that up with benchmarks?