Dave W. Plummer's RetroPad squeezes XP Notepad into 2,749 bytes

Why it matters

RetroPad turns a tiny byte count into a critique of modern software bloat, but the strongest claims still hinge on unverified details: what was counted, which XP Notepad features are matched and where the code can be inspected.

Dave W. Plummer, the programmer associated with Windows Task Manager, Zip support for Windows and the Windows NT port of Space Cadet Pinball, is the developer behind RetroPad, a tiny x86 assembly text editor that Tom's Hardware reported as a "full-feature-parity version of Notepad from XP" weighing 2,749 bytes.

That framing matters because RetroPad is not being pitched as another note-taking business, developer editor or AI writing surface. It is a systems programmer's constraint exercise: reproduce the behavior of a familiar Microsoft Windows utility in a file size so small that the implementation itself becomes the product.

Plummer is unusually well suited to make that point. A public biography identifies him as a Canadian-American programmer and entrepreneur and credits him with creating or working on several Windows-era components, including Task Manager, the Space Cadet Pinball ports to Windows NT and Zip file support for Windows. It also says he has been issued six software engineering patents and is known for the Dave's Garage and Dave's Attic YouTube channels. The throughline is not nostalgia for its own sake. It is a long-running habit of explaining Windows from the inside out.

The number is the story, and also the question

The headline number, 2,749 bytes, is the claim that gives RetroPad its force. If that figure refers to the executable, RetroPad would be smaller than many modern web assets and orders of magnitude smaller than typical GUI application distributions. The supplied report does not establish the measurement basis: executable size, compressed size, source size or another artifact. That distinction is not pedantry. In low-level software, a byte count can change meaning depending on whether the author is counting an assembled binary, a packed file, a demo payload or a repository artifact.

Tom's Hardware also uses the phrase "full-feature-parity version of Notepad from XP." That is a stronger claim than saying RetroPad opens and edits text. Windows XP Notepad was simple, but parity still implies a checklist: file open and save behavior, editing commands, search, font handling, word wrap, status affordances, encodings and the small edge cases that make a Windows utility feel native. The available material does not list that checklist, so the safest reading is that RetroPad is reported as targeting XP Notepad behavior, not that every edge case has been independently audited.

The implementation language is the other half of the claim. x86 assembly gives a programmer direct control over instructions, memory layout and calls into the operating system. It also removes much of the scaffolding that makes modern app development fast: frameworks, runtimes, packaged dependencies and generated UI layers. RetroPad's size is therefore not just a stunt metric. It is a visible trade: development convenience for control.

Why Plummer is the right protagonist

The software industry has spent two decades moving in the opposite direction from RetroPad. Developer velocity won. Apps became easier to ship, easier to update and easier to distribute across platforms, but that convenience brought layers: Electron shells, web runtimes, analytics SDKs, auto-updaters, component libraries and cloud hooks. A text editor can now arrive wrapped in more infrastructure than an entire operating-system utility once required.

Plummer's relevance is that he represents the generation of Windows developers for whom the boundary between application and operating system was legible. Task Manager, Zip integration and the Pinball port are not just trivia. They are examples of software that users treated as part of Windows itself: small, durable, instantly understandable pieces of the desktop. RetroPad sits in that tradition even if it is not a Microsoft project and even if the available reporting does not establish a commercial release, license or download channel.

That distinction should keep the story in focus. RetroPad is not evidence that modern applications should all be written in assembly. Most should not be. Assembly is expensive to write, difficult to maintain and a poor default for teams that need portability, security review and fast iteration. But projects like RetroPad expose what software teams spend, in bytes and complexity, when they choose higher-level abstractions. Sometimes that spending is rational. Sometimes it is just inherited bulk.

The missing facts define the limits

There are several facts the public report does not settle. It does not establish when RetroPad was first released or announced. It does not state whether the program runs on current Windows versions, only Windows XP-era systems or a wider range of Windows releases. It does not provide a license, repository, binary download, source listing or independent compatibility test. It does not say whether Microsoft has any involvement; the connection is Windows as the target environment and XP Notepad as the reference point.

Those gaps do not make the project less interesting. They make it more precise. RetroPad, as reported, is a compact Windows text-editor project from a developer with unusually deep credibility in Windows utility software. The serious takeaway is not that a 2,749-byte editor will replace anyone's daily toolchain. It is that one person, working close to the machine, can still make a modern software audience look twice at how much code is actually necessary to put a useful window on a screen.