Bare-Metal Compliance and the Death of Bloat

Too much modern software has become an expensive middleman. When an organisation needs a basic tool to audit endpoints, log court attendance or generate client letters, the standard reflex is to buy into recurring bloat: half a gigabyte of nested dependencies, a web browser engine wrapped round a text form, and a monthly fee. Then the first Tuesday of the month arrives. The operating system patches, the third-party wrapper breaks, the vendor points at the platform and production stops.

There is another way.

Dave Plummer, a retired Microsoft operating systems engineer, built a Notepad-style editor in 2,686 bytes: open, save, search, replace, fonts, printing. The key, he says, is that Windows already contains most of what we think of as a Windows application: menus, common dialogs, clipboard handling, edit controls, font selection and printing. A tiny native program does not bring along its own civilisation. It arrives with a lunchbox and a map of the city (watch the build).

So three single-purpose tools were built on that principle. A security auditor that reads local system settings and checks a machine's baseline against the native Windows libraries. A court attendance record generator that compiles with the compiler already on every Windows machine. A legal letter generator that lays out structured pages, fills the fields and prints through the system's own print path.

It is like machining from raw stock. The bar steel is already on the rack. Into the lathe it goes, and out comes the exact bolt needed. No flat-pack plastic from overseas, no three-week wait.

Built on the system's own libraries, the tools survive the monthly patch cycle, and there is no waiting on a vendor to fix their broken abstractions.

Every dependency a tool needs has an owner and a failure mode, and both go on the list. Dependencies never drop to zero. They only move.