Happy to see this, now that my beloved PicoCSS has been deprecated. Sumi looks really nice!
It's not a direct replacement; I fixed a lot of annoyances from PicoCSS.
Several of their new components are just classes, defeating the original purpose and contradicting the vision of Pico.
Why are the first one or two letters in headings wrapped in <em>, like the _Bl_ in "Blades"?
Why are they calling their Pico fork "anyblades/pico", when the original Pico author's post says "The Pico CSS name and logo are not covered by the MIT license. Please give your fork its own name, so users don’t confuse it with the original."?
The worst offender: What is going on with this nonsense: https://blades.dev/css/frameworks/
Utility classes: Offloaded to a separate "anyblades/ninja" repo. Core Blades stays true to original Pico (which btw used some classes like .overflow-auto).
Fork naming: The main project is Blades at https://github.com/anyblades/blades. The "anyblades/pico" repo was just an early bugfix fork created months before Pico announced deprecation.
CSS Frameworks stats: The initial percentages were calculated against respondents who actively use CSS frameworks (~4.8k devs). They have been updated to reflect total State of CSS respondents (~9k–10k), including vanilla/CSS-in-JS users.