Rendered at 07:42:02 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
meerita 10 minutes ago [-]
I don't know how they perceive the performance. I see 41 network requests. That's 2.1 MB of CSS over the wire, blocking rendering and hurting painting and loading speed. There's 400 KB of Tailwind, 87 KB of general CSS, plus another 200 KB of other general CSS. They need to embrace functional CSS properly. I'm sure they could have a single CSS file under 80 KB that renders everything.
efortis 28 minutes ago [-]
There's room for improvement still. Currently, the production build is using long-dev class names. e.g. `DirectoryContent-module__Box_3__gl6dE` could be compiled to a shorter hash like `gl6DE3a2`.
The improvement would be shipping human-readable structure to allow easier user overrides, not that hash abomination
Onavo 20 minutes ago [-]
Would you need a source map then for prod debugging?
Gualdrapo 57 minutes ago [-]
Once (like a year ago or so) stumbled upon some person's post asking for someone to help them to "fix" some section at their website. It was done !important over !important over !important over !important. Said person was really convinced all it needed was another bunch of !important because apparently that was what ai spit for them, at least at that time
eviks 13 minutes ago [-]
Unfortunately the original blog post introducing the great CSS-in-JS system being removed is not in the "Related posts" section, would be nice to compare the thinking in the two
a11ce 2 hours ago [-]
Sometimes, [GitHub] posts a [blog post in which they move away from] some terrible [way of doing things] I've never heard before, and it's a weird indirect way to learn how awful their other [design choices] must be.
If you use Vite:
https://xkcd.com/2071/