> To stay relevant, Pico CSS would need a full rewrite: plain modern CSS instead of Sass, built on features it doesn't use today (OKLCH colors, cascade layers, Popover, anchor positioning) with fallbacks for older browsers<p>Why? Why? Why? I hate how everyone seems convinced they need to adopt the latest and greatest browser features just to stay relevant. I hate oklch and I hate Tailwind popularized it. I don't care how scientifically accurate it is at representing human color perception. It's a PITA to understand a new type of color system, and learn to tweak it, especially when HSL/RGB just worked fine.
Been working on <a href="https://bamboocss.com/" rel="nofollow">https://bamboocss.com/</a> for couple of months.<p>It's build-time, Rust/Oxc, type-safe, zero-runtime CSS-in-JS, with per-route CSS splitting.
Some recent alternatives/successors/forks that are in the same vein as Pico<p>- Nimble: <a href="https://leftium.github.io/nimble.css/demo/pico.html" rel="nofollow">https://leftium.github.io/nimble.css/demo/pico.html</a><p>- Sumi.css: <a href="https://vladocar.github.io/Sumi.css/docs.html" rel="nofollow">https://vladocar.github.io/Sumi.css/docs.html</a><p>- Blades: <a href="https://github.com/anyblades/blades" rel="nofollow">https://github.com/anyblades/blades</a><p>- Oat: <a href="https://oat.ink/" rel="nofollow">https://oat.ink/</a>
All of them failed my ten second evaluation. It's amazing how many mediocre CSS frameworks that are out there.
None of them work on older browser - <a href="https://ibb.co/album/3kJP50" rel="nofollow">https://ibb.co/album/3kJP50</a><p>Ios 13.6 in my case, which was released just 6 yrs ago, 2020. For some context, flexbox gap was added in ios14.1, released in 2021. So iOS 13.6 was still usable atleast couple of years beyond that. So such frameworks utterly failing on such browsers is hilarious, given that they market themselves as minimal.<p>People keep forgetting that css3 was announced in 1999. And adoption roughly started from 2010. The css3 of that time is not the same as css3 you get to see in latest browsers. These minimal css frameworks are really useless if you don’t know what css3 features you are writing and who you are targeting.<p>And, I Haven’t even tested those in less capable browsers like dillo or netsurf, but I doubt they will even work there.<p>If you start looking into browser market share, you will quickly realise that there are millions of worldwide users who can’t use the web normally.
I really enjoyed using Pico CSS, but I understand the choice.<p>Thank you Lucas Larroche for building Pico CSS and sharing it with us.
First, I confess that I had built quite a lot of CSS Frameworks and Design Systems in my early developer life. So, this is going to be more of a personal experience.<p>Ever since Coding Assistant LLMs became pretty good (2025-Q4 - 2026-Q1), I feel that it makes very little sense to continue to use pre-defined CSS Frameworks that 'has everything.' Of course, it is still OK if the general team decides on one, and they are OK (such as the Tailwinds, MUI of the frontend world.)<p>I have used Foundation[1] and Bourbon[2] extensively. Mostly because I can break it down and take just what the project needs and keep it within a low CSS budget for any project.<p>With that in mind, in the 10+ projects that started for some of the biggest brands of the world, I just defined the CSS framework, design systems, design token, with room for extension as the project grows. Claude Code is my tool of choice for now and I just let it run overnight, tweak as the project scaffolds and finally takes about less than a week to have a complete CSS framework in just plain CSS, and JavaScript where it needs to talk to the broader frontend.<p>1. <a href="https://get.foundation" rel="nofollow">https://get.foundation</a><p>2. <a href="https://www.bourbon.io" rel="nofollow">https://www.bourbon.io</a>
<a href="https://github.com/anyblades/blades" rel="nofollow">https://github.com/anyblades/blades</a> seems to be a continuation in the same spirit
Thanks for sharing! Same spirit, same underlying code.<p>We’re actively maintaining Blades CSS on GitHub and Discord, and would love Community feedback there.<p>We also set up a dedicated page outlining key details: <a href="https://blades.dev/css/pico/" rel="nofollow">https://blades.dev/css/pico/</a>
A little sad in a way, but this seems like the right call. I haven't used Pico in a very long time, and I don't think I'd choose it today.
I haven't done frontend dev in a while, but one thing stands out to me here... they call out using OKLCH colours, which I had to look up. (For the uninitiated, this is a cylindrical projection of the also-new-to-me Oklab colour space, which appears largely unrelated to the older CIE L*a*b* colour space).<p>Do people actually use this? In particular, before LLMs ate the world, I mean. When I did frontend, it was hex, or if you felt fancy, `rgba(...)` (though at that point named colours had mostly fallen out of style).<p>Is using these less-intuitive colour encodings made more practical through the use of CSS variables?
Yes, people use it in practice. But it's not being used for the thing you're thinking of.<p>RGB is fine for specifying a color. I mean, there are issues with RGB colorspaces and whatnot, but if you need to pick the background of a page or the color of text, there's no real reason not to use RGB.<p>The problem with RGB is that it is really bad at color interpolation. You can't take the average of the red, green, and blue components of two colors and expect a usable color in the middle to come out. Instead, you need to move to a perceptual color space. CIELAB is the old perceptual color space of choice; Oklab is the new perceptual color space of choice.<p>Color interpolation is needed for things like gradients or information visualization, where you need to say things like "20% of the way between color A and color B".
> Do people actually use this?<p>Yes. OKLCH is actually MORE intuitive when creating shades because it's based around human perception. It also supports wide color spaces like P3, where rgba is, IIRC, bound to sRGB.<p>The utility of these color spaces and color functions isn't lost just because LLM. Color <i>systems</i> haven't gone anywhere.<p>Would highly recommend reading up on OKLCH if you haven't already. A lot of people put a lot of effort into promoting this and bringing it to baseline..
Well I use it on my personal site: the colors change with the weather and seasons [1]. Oklab’s so-what is that the hues are perceptually a uniform brightness, unlike HSL (which I started with) where blues and reds look a lot brighter than greens and yellows at the same saturation/lightness.<p>So in my case where color shifting is happening, Oklab actually helps. I don’t know how it’s better than HSL for simple UI elements unless maybe you can get physically brighter values that pop out more on certain screens.<p>[1]: <a href="https://joeldueck.com" rel="nofollow">https://joeldueck.com</a>
Yes, since the last couple of years. I tend to help architect and scaffold large projects that goes on for years, and changes a lot of developers, designers in its lifecycle. I was pretty confident of moving to OKLCH about 4-years ago and have have had it as default. OKLCH values are now the source of truth for these projects, and other design elements — all the way to Powerpoints (HEX/RGB) and Print (CMYK) are derived from OKLCH. There are variations but most people don’t even know the difference.<p>This started way back working with my long-term business partner and he built a pretty good tool to help visualize and tinker with it.<p>Website <a href="https://colorcolor.in" rel="nofollow">https://colorcolor.in</a><p>Source <a href="https://github.com/saneef/color-color" rel="nofollow">https://github.com/saneef/color-color</a>
<p><pre><code> Do people actually use this?
</code></pre>
Yes. I made <a href="https://uchu.style" rel="nofollow">https://uchu.style</a> after I read this blog post: <a href="https://evilmartians.com/chronicles/oklch-in-css-why-quit-rgb-hsl" rel="nofollow">https://evilmartians.com/chronicles/oklch-in-css-why-quit-rg...</a><p>I love OKLCH. Awkward to say, beautiful to look at.
Yes. And I'd argue it's <i>more</i> intuitive if all colors with the same lightness value are in fact the same lightness. Hue and chroma are pretty easy to understand too.
This is my fave article on the subject:<p><a href="https://evilmartians.com/chronicles/oklch-in-css-why-quit-rgb-hsl" rel="nofollow">https://evilmartians.com/chronicles/oklch-in-css-why-quit-rg...</a>
Pico is a great little library.<p>Thank you to the developer and maintainer<p>For what it’s worth I had to force Claude early in to use pico and not ever generate react or ornate tailwind.<p>Pico is extraordinary for standalone tools where ai can’t let complexity build out of control.<p>Maybe there’s other options but pico is what got it done, and vanilla LLMs has a hard time keeping something this simple and elegant and flexible.
Hmm. I use pico. They could use an agent to modernize it!
What a tragedy.
[flagged]
> To stay relevant, Pico CSS would need a full rewrite: plain modern CSS instead of Sass, built on features it doesn't use today (OKLCH colors, cascade layers, Popover, anchor positioning) with fallbacks for older browsers, and a native compiler that strips unused CSS and makes customization easy.<p>Does anyone know a similar project doing this?
We do: <a href="https://github.com/anyblades/blades" rel="nofollow">https://github.com/anyblades/blades</a><p>Already plain modern CSS instead of Sass, has Popover API, and CSS layers for individual components, OKLCH colors are on the way.<p>Drop-in compatible with Pico CSS (via underlying fork)
But why? Is it not relevant anymore? It's as useful and capable as it was years ago
[dead]
[flagged]
[dead]