3 ms·
When this came up a couple of months ago, I wrote https://news.ycombinator.com/item?id=28860500 https://news.ycombinator.com/item?id=28860500: > Not fond of Pi
by chrismorgan 5y ago
When this came up a couple of months ago, I wrote https://news.ycombinator.com/item?id=28860500 https://news.ycombinator.com/item?id=28860500:
> Not fond of Pico.css’s weight, though: over 50KB, nowhere near as lightweight as the name suggests (even if it’s above-average compressible, 8KB gzipped—but I wouldn’t count even 8KB uncompressed as pico); in this case, if you flatten the variables and strip unused code, you’re left with under 4KB (~1.4KB gzipped). Lots of bloat from unused light mode support, things like form controls, and a fair bit of frivolous custom properties usage. This is the sort of place where I see the appeal of the likes of Tailwind, because they generate such huge amounts of CSS that you just about have to use an unused style remover. But it is another build step, and contrary to the deliberate intent here.
- deleted 5y ago[deleted]
- deleted 5y ago[deleted]
- oxalorg 5y agoI agree. That is why I actually just decided to use different css files for different themes in sakura.css (it comes in at 3.8k / ~1.8k gzipped) This also means that they can easily be used by others as well [1]. Have gotten some folks contribute their own themes over the years. I also had friends who didn't want to understand CSS, and adding in media queries, variables, and dark mode support would only just confuse them even more. [1]: https://github.com/oxalorg/sakura/tree/master/css https://github.com/oxalorg/sakura/tree/master/css