Leftium
Joined 16 years ago
Joined 16 years ago
Perhaps because it's not a stand-alone tool? (Although there are stand-alone tools that accomplish this)
I guess the most likely reason is the exact trigger phrases aren't present
It's not a direct replacement; I fixed a lot of annoyances from PicoCSS.
When shutting down, Windows optimizes the next start by caching some stuff. So it is not a true, clean restart.
On a restart, this caching does not happen.
Sources:
- https://www.youtube.com/watch?v=lUIhzACQDAc
- https://learn.microsoft.com/en-us/windows/win32/power/system...
The one demo'ed in the video is BOYA BY-GM18CU (https://www.amazon.com/dp/B0BF969RVP)
That one captures whispers. I've heard other devices can dictate based on vibrations from your neck/chest.
If the site adds a PWA manifest, Android (Chrome/Google app) will show a prompt to install as app on load. Also PWA install will be available for older iOS.
I made a simple tool that generates a minimal PWA manifest: https://logo.leftium.com/logo
The main annoyances:
- oversized buttons
- 100+ root custom properties in devtools
- fighting against too many breakpoints (unpredictable font/container sizing)
---
I also changed/added some features:
- much smaller core: only 4.1 KB Brotli
- CSS cascade layers so app CSS can override more easily
- a surface color system (a la Open Props)
- OKLCH colors with auto derived hover/focus states and light-dark() theming
- centered layout with real gutters, plus content bleed outside gutters
- .no-nimble opt-out class (instead of .pico opt-in)
- ability to configure universal control-density (buttons, inputs, selects)
So if you can't see it: feature-comparison matrix plus notes from migrating several real projects from Pico:
https://github.com/Leftium/nimble.css/blob/main/specs/pico-m...
- oversized buttons
- 100+ root custom properties cluttering DevTools
- fighting against breakpoint-heavy font and container sizing
- container "padding" that could disappear at exact breakpoints
- having to fight framework styles with specificity
Nimble uses more compact controls, ~20 semantic variables, simpler grid-based centering with real gutters, and cascade layers so normal app CSS wins.
---
I also added some features/changed:
- much smaller core: Nimble is only 4.1 KB Brotli
- cascade layers, so normal app CSS can override the library without specificity fights
- a surface hierarchy for page/card/input/overlay backgrounds (a la Open Props)
- OKLCH colors with derived hover/focus states and light-dark() theming
- centered layout with real gutters, plus bleed-edge, bleed-wide, and bleed-full
- .no-nimble to opt third-party component subtrees out of Nimble styling
- shared control-density customization for buttons, inputs, selects, etc.
- .nc-join for visually joined controls without coupling that styling to ARIA role="group" (this kept confusing coding agents; technically they should not be coupled)
---
Feature-comparison matrix plus notes from migrating several real projects from Pico: https://github.com/Leftium/nimble.css/blob/main/specs/pico-m...
But it's not a drop-in replacement. (I fixed several annoyances I had while using PicoCSS.)
leftium.com
Leftium: The Element of Creativity!