YHK - yet another hacker news clone

Pico CSS is no longer maintained

43 points henrid 1 hour ago 13 comments

steve_adams_86 56 minutes ago | parent

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.

nchmy 24 minutes ago | parent

What would you choose?

Retr0id 54 minutes ago | parent

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

anydigital 20 minutes ago | parent

Thanks for sharing! Same spirit, new home.

We’re actively maintaining Blades CSS over on GitHub and Discord, and would love community feedback.

We also set up a dedicated page outlining key details: https://blades.dev/css/pico/

u8 46 minutes ago | parent

What a tragedy.

eterps 41 minutes ago | parent

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

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

psadri 30 minutes ago | parent

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

0c3ca83 10 minutes ago | parent

Yeah, but why? Writing code for agents to use isn't fun, and buying tokens for it is a waste of money.

smlx 26 minutes ago | parent

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

anydigital 4 minutes ago | parent

We do: https://github.com/anyblades/blades

Already plain modern CSS instead of Sass, has Popover API, and CSS layers for individual components, OKLCH colors are on the way.

verandaguy 5 minutes ago | parent

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?