- Mental tools for your mind: turn a mouthful like "Shift+Control+Option+Command+C" into "Giga+C"

- Software tools for your fingers: easily press Shift+Control+Option+Command+C using just two fingers from a single hand! (via Karabiner rules)

I renamed Hyper and Meh because the modifier key combinations varied depending on the source. I picked the most logical combination: Giga == Shift + Mega

I picked the names/symbols and even modifier combinations so they would be easy remember. Explained in detail: https://leftium.github.io/megakey/modifiers

---

In addition, I created 3 more pseudo-modifier keys. They are very handy for existing shortcuts. For example:

- Wish+Space: TrellisWM "Show everything"[1] (Ctrl+Option+Space)

- Chaos+N: Chrome "Add tab to new split view" (Cmd+Option+N)

- More useful pre-existing shortcuts: https://leftium.github.io/megakey/shortcuts

[1]: https://trelliswm.app/docs/#shortcuts

Comments URL: https://news.ycombinator.com/item?id=50207489

Points: 2

# Comments: 0

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

Comments URL: https://news.ycombinator.com/item?id=50110565

Points: 1

# Comments: 1

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

Comments URL: https://news.ycombinator.com/item?id=49974057

Points: 4

# Comments: 0

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

I was trying to figure out what you meant by "declarative" because CSS is declarative. (My understanding is: "declarative means you say (declare) what you want, but not how to get it." Usually SQL is the poster child of declarative languages.)

I think you're really talking about a mix of preferring data (vs actions/calculations) and DSLs (which aren't necessarily declarative)

Eric Normand has some thoughts you might appreciate:

- How a problem might take 1000 SLOC to solve directly, but only 10 SLOC with a DSL (plus up to 500 SLOC for the DSL itself; still fewer lines total) https://ericnormand.me/podcast/magical-leverage-languages

- Data vs calculations vs actions: https://ericnormand.me/podcast/what-is-an-action

---

I think data can be very powerful. For example, someone explained to me:

> I've been helping my non-tech father with Home Assistant. I've honestly been shocked with how far "community extensions" + "user configuration" can take you. Every time we hit a bug, I go "time to hit github" but without fail chatgpt and him are able to tweak a setting to get it working.

If you make your system configurable (config==data), you can skip the whole compile/build step!

Here is an example of a calculation written imperatively. It remains easy to reason about because the actions don't leak out of the function:

    function add(ns) {
        let total = 0
        for (const n of ns) {
            total += n
        }
        return total
    }

https://ericnormand.me/podcast/what-is-an-action

https://livebook.manning.com/book/grokking-simplicity/chapte...

Because I see AI coded software everywhere: HN has been complaining about the recent influx of Show HNs due to AI. Take a specific product category: there are about two new dictation apps on Show HN every week.

Here are my theories:

- adobe/office are simply too complex for AI to replicate (as of now). Theo Browne has been testing all the frontier models with a relatively simple fish game. The results have been subpar, at best. I don't think anyone would prefer the AI-generated games over the original. Even if the AI-generated version was free.

- Most AI-coded software won't be distributed like classic software. Instead of a bag of hundreds of features (adobe/office), AI will be used to create the specific 5% of the features a single user really needs (home-cooked software). The software may even be per project or even per task. Why spend 20X to 100X the tokens/time when you only need a small subset of the features?

- AI may not be able to replace human "taste" or design. There is a lot of design that went into adobe and office. I don't think AI can fully understand all the "why's" of these designs. We can already kind of see this with open source: Gimp and LibreOffice are alternatives to adobe/office. Yet most people prefer the paid options.

- Even if AI solved coding, there are other barriers like marketing.

Some examples:

- I built my perfect window management system with the help of AI. It suits my very specific needs very well, but it's nowhere near ready for distribution. So this is AI-generated software no one else will ever probably see.

- Going with the home-cooked meal analogy: there is a dish served at all Chinese restaurants in Korea: jjajangmyeon. However you can't find it in China because that dish is only found at home, not at restaurants in China.

So my advice is to highlight the major benefit over the iOS weather app that ships with every iPhone.

The only major difference I could see is the data source. Did you intentionally not use Apple WeatherKit? (If so, what was the rationale?)

- Comments have 3 LOD (L:full, M:single line, S:collapsed)

- Optimal default LODs

- Simple to expand groups of comments (direct replies, comment thread ("spine"), full sub-tree)

- Highlight specific users like OP, or other interesting users

- Search for text within thread (automatically expands LOD)

- Highlights new comments (since last visit or set time)

It matches the way I want to read HN comments, anyways.

(According to recent article on HN[1]. So LLMs _are_ compression!)

[1]: https://hn.leftium.com/i/49263497

1. Click menu bar time/clock

2. Click Edit Widgets...

3. Search for "Codexbar"