Microsoft hasn't had a coherent GUI strategy since Petzold

Original Article ↗ Hacker News Discussion ↗

Perceived incoherence of Microsoft’s GUI strategy

  • Many see a long-running pattern of Microsoft creating, hyping, then semi-abandoning GUI stacks (Win32, MFC, WinForms, WPF, Silverlight, UWP, WinUI, etc.), with no single “blessed” path.
  • Developers describe internal politics and “impact”-driven incentives as favoring new frameworks over finishing and maintaining old ones.
  • Some argue Windows GUI inconsistency (multiple visual styles, ancient dialogs alongside new UIs) is now user-visible proof of this churn.

Native vs web / why target Windows at all

  • Several participants ask why anyone would build Windows-only GUIs when the web runs everywhere and can be wrapped as PWAs or Electron/Tauri apps.
  • Pro‑web arguments: largest audience, deployment ease, avoidance of app stores, strong DX/UX with modern JS, acceptable performance for most apps.
  • Pro‑native arguments: better performance, RAM usage, deeper OS integration, offline behavior, more predictable behavior than browsers; some claim Electron-class apps feel sluggish and bloated.

Evaluations of specific Windows GUI stacks

  • Win32 + raw message loops: considered ugly/low-level but rock-stable and still viable.
  • WinForms: widely praised as the simplest, fastest way to ship traditional Windows GUIs, with strong RAD tooling and third‑party controls; main complaints are DPI and lack of hardware acceleration.
  • WPF: very polarizing; praised for data binding, XAML, and modern rendering, but also condemned as verbose, hard to debug, slow on typical 2000s hardware, and never fully finished.
  • WinRT/UWP/WinUI: seen as a major misstep tied to the failed Windows 8/RT and Store push; APIs were restricted, deployment painful, and the model perceived as aimed at tablets over existing desktop users.

Comparisons to other platforms

  • Apple is viewed as more consistent in design systems and long-term framework support (AppKit/UIKit/SwiftUI), but not without serious issues (SwiftUI performance, visual changes like “Liquid Glass”).
  • Linux desktops (KDE/GTK/Qt) are called both “more coherent” and “also churny,” depending on the commenter; many prefer Qt/GTK as stable cross‑platform options.

Article quality and AI concerns

  • A large subset of commenters believe the blog post (and especially its final infographic) is LLM‑generated “AI slop,” citing writing style, contradictions, and the graphic’s nonsense labels.
  • Others find the historical catalog of frameworks useful despite the style issues.