Former Microsoft CTO laments: Windows has become a mess! 14 changes over 14 years, with 17 types of GUI coexisting

When trading stocks, rely on Jin Qilin analysts’ research reports—authoritative, professional, timely, comprehensive—helping you uncover high-potential themes and opportunities!

（Source: Kuai Technology）

Kuai Technology, March 25 reports: Former Microsoft CTO and having worked at Microsoft for 23 years, Jeffrey Snover, recently published a long-form blog post that systematically reviews Microsoft’s repeated shifts over the past several decades in GUI (graphical user interface) design, revealing why the Windows development ecosystem has moved toward fragmentation.

First, rewind the timeline to the 1980s. At the time, Win16 and Win32 APIs provided a consistent development paradigm for all Windows developers. Developers only needed to learn one set of things to cover nearly all Windows application scenarios.

The 852-page “Programming Windows,” written by technical author Charles Petzold, is considered the bible for desktop application development.

By the 1990s, Microsoft attempted to break through the limitations of Win32 with technologies such as MFC, COM, OLE, and ActiveX. Snover pointed out that these component architectures “have permeated every corner of Windows development, introducing unprecedented cognitive complexity.”

At developers’ conferences, Microsoft’s technical narrative became disjointed. Snover, without mincing words, described the keynote talks of that time as a “keynote clusterf*ck.”

In 2003, Microsoft presented its technical vision for Windows Longhorn. Among them, Avalon (later renamed WPF) was a GPU-accelerated XAML vector rendering subsystem—its technical strength was formidable. However, in August 2004, Microsoft suddenly changed course, requiring all new development to use C++.

Although WPF was released with Windows Vista, Windows Shell itself did not adopt it. This decision planted deep rifts between the Windows engineering team and the .NET team.

Snover noted that internal conflicts ultimately led to WPF being abandoned, Silverlight dying, and UWP (Universal Windows Platform) being doomed to fail the moment it was born.

In 2007, with WPF already having proven its capabilities, Microsoft pivoted again and introduced Silverlight.

In 2010, Microsoft suddenly announced that Silverlight was not suitable for cross-platform development—HTML5 was the future direction. Silverlight would only be used for Windows Phone development, and many developers who had bet heavily on Silverlight were caught off guard.

Fast forward to 2012, the release of Windows 8. It introduced the WinRT runtime based on native C++. The Windows team’s hostility toward .NET caused the decade-long investment in it to be discarded instantly. Snover described the confusion at the time like this:

“Microsoft is telling two stories at the same time internally. The Windows team is working on WinRT, while the .NET team is pushing WPF. Different buildings, different vice presidents, different roadmaps.

What developers heard at //Build 2012 was: the future is WinRT. At the same time, HTML+JS are first-class citizens. At the same time, .NET can still be used. At the same time, C++ is back. At the same time, you should write Metro apps. At the same time, your WPF code runs great. This isn’t strategy. It’s ‘The Hunger Games’—six teams are competing for your attention.

Enterprise developers took one look at UWP’s sandbox mechanism, mandatory app store distribution, and the missing Win32 APIs, turned around, and left. ”

Snover pointed out that over the past 14 years, Microsoft has pivoted 14 times in recommending Windows GUI frameworks. Today’s Windows platform coexists with 17 GUI technologies, covering 5 programming languages:

Microsoft’s native frameworks: Win32 (1985), MFC (1992), WinForms (2002), WPF (2006), WinUI 3 (2021), MAUI (2022)

Microsoft’s web hybrid solutions: Blazor Hybrid, WebView2

Third-party solutions: Electron (used by VS Code, Slack, Discord; Snover specifically notes that this is currently the most widely deployed desktop GUI technology on Windows, and Microsoft has nothing to do with it), Flutter (Google), Tauri, Qt, React Native for Windows, Avalonia (used by JetBrains, GitHub, Unity; Snover sarcastically remarks that these developers “don’t wait for Microsoft anymore”), Uno Platform, Delphi, Java Swing/JavaFX

Snover coined the term “boof-a-rama” to describe the current situation as smart people doing something foolish. He emphasized that the technologies Microsoft rolls out are often not inherently bad. What truly kills them isn’t technical flaws, but internal politics, announcing pivots too early at developers’ conferences, and chaotic commercial strategy.

Petzold’s “Programming Windows” stopped being updated after the sixth edition in 2012 (covering Windows 8/WinRT). Perhaps that is the best footnote to this kind of unpredictable fragmentation.

Snover joined Microsoft in 1989. He held roles including Partner Architect, Distinguished Engineer (2009), Technical Fellow and Chief Architect (2015), and CTO (2019). In 2022, he left to join Google. In 2025, he officially retired. Given what he knows about Microsoft’s internal operating model, the credibility of this blog post is self-evident.

A massive amount of information and precise analysis—right on the Sina Finance APP