Have some fun stuff to share for fellow light mode terminal lovers: we call it Automatic Contrast Correction. Users of light themes will have felt my pain. Developers have generally designed text interfaces for dark mode terminals. There are many examples in the tui apps I use everyday: `lsd`, `btop` (with theme bg off), even my beloved `lazygit` has some suss legibility out the box. The issues are so bad, I generally switch to a dark theme to read stuff. Automatic Contrast Correction fixes this issue by evaluating contrast at runtime between whats being sent from the server to the macOS client versus the theme mode the user is running. Our correction pipeline finds low contrast foreground/background combinations, does some oklab magic, hue rotation towards theme-colors, contrast checking and produces an end result of theme-harmonious, perfectly WCAG-approved legible text. All this happens in nanoseconds and is then cached for performance. It's built right into the @superlogical client. (Screenshots above show ACC off and on)

i think we're all really particular about our terminal environment. we're building the @superlogical clients to have beautiful defaults but also quite a few levels of customisation. this ranges from full liquid glass embrace to totally solid system palettes, through to our 41 custom themes which tint the entire application. we also have two modes of density: our "islands" for terminals (comfortable mode) and a more traditional single pixel border (compact mode).

I'm really not one for frills when it comes to using agents. I don't use MCP servers, and I don't have dozens of skills installed - just a select few... `/product-description` is one of them. uniquely helpful and good. It goes feature-by-feature in an application to create behaviour specs and then verify against what is running. A sorta integration test superpower.

My software design process these days is literally @tldraw / notebook → code. The bar for quality software has only gone up since the advent of ReallyGoodModels, and designing in the medium of the finished product really is the best way to create quality software.

The worst part of the otherwise excellent Logitech mice & keyboards has always been the software. Nice to see an open source, local-only desktop app alternative launch

The state of TUI user theme support is kinda all over the place, even in some of the most popular apps I use everyday. Overriding user palette, no detection of light/dark mode change, very often no light theme support at all. I’m working on a library to make this fool proof for developers to support, with adapters for Zig, Go, Rust, Node, c++. It exposes simple events to monitor theme & appearance changes, access to the ANSI palette and the ability to change opacity from base colors. Here’s a screenshot before and after (running in @superlogical web client) of mainline btop and my fork of btop running this new library. btop’s light theme support is kinda non existent but now it’s usable (still needs tweaks). Still some work to do but hopefully something releasable soon.

there's a phenomenon in engineering called the "zenith before obsolescence": when a technology reaches its most perfected form just as it’s about to be replaced. The Eiffel Tower was that for construction in wrought iron. Disco was that for the Aqua-era.

After years being speakerless, I bought these edifier M60s for my home setup. Holy shit they sound so good I can't believe what I was missing. Best of all they just connect to the studio display via usbc. Gonna go back to listening to Burial now.

Unfortunately this is true (believe me I’ve tried). Non-native macOS apps just exist on a different (lower) plane to native ones. A mediocre but native app is always superior to a “very good” non-native app

From desktop to web, and back again. We're engineering each @superlogical client to feel native to its platform and the best possible expression of what that environment has to offer. For web, that means a responsive ui with a webgl+libghostty powered terminal emulator.