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.

https://github.com/anyblades/blades seems to be a continuation in the same spirit

What a tragedy.

I really enjoyed using Pico CSS, but I understand the choice.

Thank you Lucas Larroche for building Pico CSS and sharing it with us.

Hmm. I use pico. They could use an agent to modernize it!

> 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.

Does anyone know a similar project doing this?

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).

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).

Is using these less-intuitive colour encodings made more practical through the use of CSS variables?

Some alternatives/successors/forks that are in the same vein as Pico

- https://leftium.github.io/nimble.css/demo/pico.html

- https://vladocar.github.io/Sumi.css/docs.html

- https://github.com/anyblades/blades

- https://oat.ink/