archinstall is a Python application and library for automated and interactive installation of Arch Linux. In production it runs as a root-level CLI/TUI wizard via the `archinstall` console script, guiding users through disk partitioning, LUKS/LVM encryption, BTRFS subvolumes, bootloader installation (systemd-boot, GRUB, limine), network configuration, user/sudo creation, mirror selection, pacman settings, and desktop/server profile installation. The same core is exposed as a reusable library, with entry points in `archinstall/scripts/guided.py`, `minimal.py`, and `only_hd.py`, and JSON configuration/credentials files enabling fully automated, headless installs. The installer orchestrates real system tools such as `parted`, `lsblk`, `pacman`, `systemd-nspawn`, `btrfs`, and `lvm`, and validates configuration with Pydantic and dataclass models.
Rufus is a Windows-native GUI application for creating bootable USB drives and formatting removable media. In production it is a single binary that drives raw disk I/O through Win32/NT APIs, parses ISO/WIM/VHD/FFU images, decompresses archives in many formats, formats to FAT/FAT32/NTFS/UDF/exFAT/ReFS/ext2/3/4, and writes MBR/PBR/bootloaders such as Syslinux and GRUB. It also implements Windows-specific features such as UEFI Secure Boot revocation updates, Windows To Go support, VSS snapshots, and dark-mode UI. Architecturally it is a classic monolithic C application: an autotools/VS build produces one executable with a Win32 dialog UI, a resource-based localization system, and tightly coupled modules for device enumeration, formatting, ISO mounting, and WIM application. The repo vendors a large collection of self-contained C libraries (wimlib, libcdio, ext2fs, ms-sys, syslinux libinstaller, bled decompression, getopt) and adapts them for Windows raw-block I/O. Runtime dependencies are Windows system DLLs, Microsoft symbol-server downloads, UEFI revocation databases, and optional network fetches of boot components. The project is actively maintained with CI workflows for VS2026 and MinGW, CodeQL, Coverity, and dependabot. Its code quality is characterized by defensive low-level Windows programming, careful handling of version-dependent APIs, and extensive real-hardware compatibility work. The main risk is technical drift: many vendored dependencies are snapshots of older upstream libraries, and several modules rely on undocumented or semi-documented Windows behavior.