| Maker here. Some technical context: Process discovery uses sysctl + NSRunningApplication. Kill signals go through POSIX kill() with SIGKILL — no graceful shutdown, just immediate termination. For the I/O monitor, I'm polling per-process disk and network stats via IOKit. The fuzzy matching was the trickiest part. macOS processes often have different executable names vs. what Activity Monitor shows (localized display names). PIDKill checks against the executable name, the display name, and the full path — so partial input like "chrome" or "adobe" usually catches what you want. I went with DMG + Gumroad license keys instead of the App Store. At $3.99 the 30% cut would have made it hard to justify the time spent maintaining it. One thing I'm still iterating on: the Inspect tab (I/O monitor) can record activity and replay it frame-by-frame. It's useful for debugging intermittent disk/network spikes, but I'm not sure how many people will discover it. Feedback welcome on that. Question for HN — what processes drive you crazy on macOS? I seeded the initial use cases from my own pain (Xcode, Simulator, Adobe, Chrome), but I'm sure there are offenders I'm not thinking of. |