Why desktop software still matters
Twenty years after glassy desktop chrome peaked, the OS patterns we took for granted are still the interaction model we're chasing.
I spent three weeks last March rebuilding a calendar widget in a cross-platform shell, then threw it out and rewrote the whole thing in a native toolkit. The native version shipped at 1.2 MB — icons, localization strings, and all. The shell build, with its transitive dependency tree, clocked 187 MB before it could render a single date picker. That moment — staring at two folders side by side in the file manager — crystallized something I had been avoiding for years.
The physics of native chrome
Desktop software has something web apps, for all their deployment speed and zero-install convenience, still cannot replicate: a direct line from user intent to pixel response. When you click a title bar in a native window, the system routes that event through one driver stack — not a compositor, a scripting engine, a virtual document diff, and a browser repaint. That eight-millisecond gap is invisible to synthetic benchmarks but immediately legible to fingers. Users who switch from native apps to web-based replacements routinely report a vague sense that something feels off — not broken, just slower than it should be.