April 5, 2026
Choose your fighter: Win32 vs Web vs Chaos
Microsoft Hasn't Had a Coherent GUI Strategy Since Petzold
Dev room goes silent as fans split: old-school, web apps, or is Windows just lost
TLDR: A viral rant claims Windows hasn’t had one clear way to build apps since the 1980s, reigniting old wounds about Microsoft’s many toolkits. Comments split between sticking with classic tools, going all‑in on web apps, or giving up, with jokes about Bill Gates and AI writing adding spice.
A brutal think piece says Microsoft hasn’t had a clear way to build Windows apps since the 1988 “one book to rule them all” era—and the comments lit up like a power strip. The room-silence anecdote (“WPF? WinUI 3? Electron?”) became a meme, but the real fight is over what to build with now.
One camp cheers the long tail of anything works: “You can still write a Win32 app”, and Microsoft pushed the web so hard it basically helped invent “web app” life—think AJAX (web pages update without reloading) and modern CSS layouts. Another camp growls, “Just use Windows Forms,” calling it the fastest, cleanest way to ship a desktop app in C#. The futurists? They shrug and say wrap it in a browser shell (Electron) and move on.
Then the drama: one commenter roasted the author’s prose with “These LLMs are just awful at writing,” while another asked the ultimate burn—does Bill Gates even use Windows anymore? Meanwhile, someone name-dropped ex-Windows boss Steven Sinofsky’s take on the mess, linking to his thread. Between nostalgia for the simple Petzold era and flashbacks to the Longhorn/Vista reset, the vibe is clear: Windows devs want one answer, not ten—and they’re tired of guessing.
Key Points
- •The article contrasts a past era of clear Windows UI guidance (Win16/Win32 documented by Petzold) with current ambiguity over desktop app frameworks.
- •It identifies 1990s technologies like MFC (1992), OLE, COM, and ActiveX as increasing complexity rather than offering a unified GUI framework.
- •At PDC 2003, Microsoft presented Longhorn’s pillars: WinFS, Indigo, and Avalon (later WPF/XAML) as a comprehensive vision.
- •In August 2004, Microsoft reset Longhorn development to the Windows Server 2003 codebase; an internal memo by Jim Allchin called Longhorn “a pig.”
- •The article states leadership discouraged managed code in Windows post-reset, WPF shipped with Vista but wasn’t used by the shell, and internal tensions affected WPF, Silverlight, and UWP.