2 ms·
> whereas every asynchronously loaded <div> in the first case is gonna be 3.8 KB. An inventory with 3,176 items will take 12.2 MB to fully load WITHOUT product
by troupo 3y ago
> whereas every asynchronously loaded <div> in the first case is gonna be 3.8 KB. An inventory with 3,176 items will take 12.2 MB to fully load WITHOUT product descriptions e.g. user decides to search empty string and scroll all the way to the bottom.
If you're asynchronously loading something, why are you loading divs, and not JSON which you then display on the page?
> fter the front page is presented, so the first thing visitor sees is a quick loading page, the 2 to 4 second load happens in the background, they click a link, BOOM next page loads in its full-featured, one-or-two-human-readable-class-per-element glory with the Sneaky Load Giant CSS as an already-cached dependency.
This has nothing to do with Tailwind, css classes, or even JS frameworks.
> outside of every paragraph (instead of a single, well-defined paragraph class that could even inherit common custom properties)
Again, this has nothing to do with Tailwind, and everything to do with:
- CSS sucks at components
- CSS sucks at scoping
- CSS sucks at nesting
- CSS sucks at namespacing
Literally nothing is stopping you from applying a global style even if you use Tailwind. Moreover, the authors of CUBE methodology [1] suggest Tailwind for utility classes [2]
[1] https://cube.fyi https://cube.fyi
[2] https://buildexcellentwebsit.es https://buildexcellentwebsit.es