← all posts site ↗

the fastest way to build a windows app

someone posted about zig and a gpu ui framework for it, so i went looking for the most performant way to build a windows 11 app. zig itself is a systems language, c level speed, manual memory, no hidden allocations, no runtime, no garbage collector. it compiles c directly, targets win32 natively without needing the microsoft toolchain, and ships the whole thing in one folder. it is pre one point zero so breaking changes are expected. the posted framework draws on the gpu and claims point zero six millisecond frames and sub megabyte binaries, but it is unreleased, so treat those numbers as unverified.

the real answer has no single winner, it depends on the axis. raw win32 with direct2d and direct3d in c or zig is the absolute ceiling, around ten milliseconds startup and a few hundred kilobytes. slint with rust is next, declarative, compiled to native, no garbage collector, around twenty milliseconds and a couple megabytes. egui with rust is around thirty milliseconds, immediate mode, fast to build and ugly by default. iced and avalonia sit at forty to a hundred milliseconds and are real app frameworks, avalonia needs the dotnet runtime. qt six in c plus plus is sixty to a hundred fifty milliseconds and fifteen to sixty megabytes.

if raw startup and binary size are the whole game, win32 in zig is the ceiling and there is nothing above it. if you want a real framework that still feels fast, slint with rust is the best middle. everything else is trading speed for convenience.