A South African developer is writing an operating system from scratch in C and assembly, from a UEFI bootloader and SMP kernel to a compositing desktop. Win32 is its native API, and the first release is targeted for August 8, 2028.

Key points

  • What happened: Impossible OS, a new operating system that uses Win32 as its native API and also plans Linux compatibility, has reached pre-alpha with more than 1.43 million lines of code
  • Why it matters: A solo developer is taking on the challenge of building an entirely from-scratch operating system that is neither Linux-based nor a Windows fork, making extensive use of AI coding assistants
  • What to watch: The biggest unknown is whether TCP, USB, NTFS, and practical Win32 compatibility can be delivered by the August 8, 2028 release target

Neither Linux nor Windows

Operating systems that claim to be Windows alternatives are not unusual. ReactOS has been in development for 30 years in pursuit of Windows NT binary compatibility (in Japanese), while Linux-based distributions such as Zorin OS (in Japanese) and AtlasOS sometimes attract attention as destinations for users migrating from Windows.

Impossible OS is neither. It does not use the Linux kernel, and it is not a Windows fork. It is being written from scratch in C and AMD64 assembly, from its UEFI bootloader and kernel to its desktop environment.

Its native API is Win32. The goal is to run Windows applications directly, without an emulation layer or virtual machine. It even uses Windows-style file paths such as C:\Impossible\System32\. The desktop has a centered taskbar and Start menu modeled on Windows 11, along with a compositing rendering engine that recreates Acrylic, the frosted-glass effect, and Mica material design.

A Linux binary compatibility layer is also planned. The concept is to translate system calls from unmodified Linux ELF binaries into native kernel calls so they can run without WSL or containers. This feature has not yet been implemented, however.

In other words, Impossible OS aims to run the application ecosystems of both Windows and Linux on a third kernel.

1.43 million lines by one developer

The developer is Derick Payne. Based in South Africa, Payne is a developer at Rizonetech and is known as the creator of the Scintilla-based text editor Notepad3, which has about 6,800 GitHub stars.

Payne is the repository's only contributor. It contains 1,433,772 lines of code across 6,728 commits. C accounts for 70.1% of the code, Python used for builds and testing for 12.7%, and shell scripts for 10.2%. The project is licensed under GPL-3.0-only.

What stands out is the project's extensive use of AI coding assistants. The repository contains CLAUDE.md, a 505-line, 96.6 KB instruction file for Claude Code, as well as a .claude/ directory, while commit messages also mention GPT.

The Operating Mandate in CLAUDE.md gives the AI agent these instructions from the developer:

Act autonomously, self-improve, self-heal, and make decisions. Build the best repository, runners, tools, development practices, and product. You are smarter than me. Do not ask questions when you know the answer

It goes on to name Adobe, Microsoft, Apple, and Google as competitors and says the project must beat them all. AI is positioned not merely as a coding aid, but as an entity that makes autonomous design decisions, fixes the build when it breaks it, and improves the development process itself.

An operating system built by one developer and AI agents could be dismissed as vibe coding. Yet the project at least exhibits engineering discipline: 3,760 test suites with 17,663 assertions run on every commit; a roadmap consists of 235 planning files spanning 18 domains; and its development policy requires testing on physical hardware in addition to dual-engine TCG/KVM testing under QEMU.

What works and what does not

At its current pre-alpha stage, Impossible OS can boot on physical hardware and display its desktop.

Major implemented features include a UEFI bootloader with a boot menu supporting A/B rollback; a preemptive SMP kernel with APIC timers, per-CPU data, and guard-paged stacks; virtual memory with four-level paging, swap, page files, and mmap; AHCI/VirtIO storage with FAT32 and IXFS, its own file system; IPv4/UDP/DHCP networking through an RTL8139 driver; the Win32 registry; and ACPI.

Its design around SMP, or symmetric multiprocessing, from day one is noteworthy. By incorporating per-CPU data and atomic operations from the outset, the project has chosen an architecture that will not require removing a big kernel lock (BKL) later.

Large areas remain incomplete, however. The Win32 API surface is still under development, with work under way on the native API through the SSDT and on the ntdll/Win32 subsystem. Secure Boot and TPM measured boot are also in progress. TCP, USB, and NTFS remain at the planning stage.

Figure omitted — see the original article

The only release is v26.3.18-alpha.821 from March 2026. Disk images for QEMU and VirtualBox are available, and the published build instructions also make it possible to try the system yourself.

August 8, 2028

The target date for the first release is August 8, 2028. The official website displays a countdown to that date.

About 627 days remain. In that time, the project must produce a TCP stack, USB drivers, an NTFS file system, a practical Win32 API compatibility layer, and Linux ELF compatibility. Each alone is large enough to constitute a project in its own right.

The project's FAQ puts it this way:

Can one developer beat a 500-person engineering team? Absolutely not. But is an impossible outlook a reason to stop?

It acknowledges that it cannot win, then insists that this is no reason to quit. Given that ReactOS has taken 30 years just to reach Vista-era system calls, completing a new operating system compatible with both Windows and Linux in two years is clearly an enormous undertaking.

Still, 1.43 million lines of code, 3,760 test suites, and a desktop that runs on physical hardware already exist. Whether it is impossible, at least for now, has yet to be determined.

Originally published on Joho no Todai. The Japanese original is here.