5 ms·
Various comments and links throughout the discussion of this post indicate that the problem is a mix of the sheer number of nodes and css. It has nothing to do
by humpty-d 1y ago
Various comments and links throughout the discussion of this post indicate that the problem is a mix of the sheer number of nodes and css. It has nothing to do with React or being a React SPA, which it's also not, unless you have some proof otherwise.
- bythreads 1y agoReact and the most commonly used pattern inherently promotes an way to complex html Node structure and shitty css, especially if stuff like tailwind is used. Now you CAN so it so that is not the case, but tbh i have never seen that in the wild -
- troupo 1y agoLol. If anything, Tailwind isn't shitty CSS (because it's a very limited number of classes) unlike the gazillion one-off classes that CSS-in-JS or even BEM encourages Edit: here's a good investigation on a real-enough app https://www.developerway.com/posts/tailwind-vs-linaria-performance https://www.developerway.com/posts/tailwind-vs-linaria-perfo...
- typpilol 1y agoYes what's with his comment? Tailwind is probably one of the best considering you can use Vite to literally strip out all unused css easily. And I think tailwind v4 does this automatically