Former Microsoft CTO Slams Windows: 14 Years of Chaos, 17 Different GUI Frameworks Coexisting
Jeffrey Snover, former Microsoft CTO with 23 years at the company (1989-2022), has published a scathing critique of Windows' development trajectory, calling it "a recipe for boof-a-rama" -- his ter...
Jeffrey Snover, former Microsoft CTO with 23 years at the company (1989-2022), has published a scathing critique of Windows' development trajectory, calling it "a recipe for boof-a-rama" -- his term for smart people doing stupid things.
The Key Timeline
1980s: The Golden Age
- Win16/Win32 API provided a consistent development paradigm
- Charles Petzold's "Programming Windows" (852 pages) was the developer bible
- One platform, one paradigm -- developers learned once, coded everywhere
1990s: Complexity Creep
- MFC, COM, OLE, ActiveX added unprecedented cognitive complexity
- Snover called keynotes "Keynote clusterf*ck"
- Developer ecosystem began fragmenting
2000s: The Pivot Parade
- 2003: Longhorn vision with Avalon (WPF) -- powerful GPU-accelerated XAML
- 2004: Sudden pivot to C++ for all new development
- 2007: Silverlight launched despite WPF proving itself
- 2010: Silverlight declared dead for cross-platform; HTML5 "is the future"
- 2012: Snover's description -- "This isn't strategy, this is The Hunger Games"
Present: Complete Fragmentation
Windows currently has 17 different GUI frameworks coexisting:
- Win32, WPF, UWP, WinUI 3, MAUI, React Native, Electron, etc.
- No clear "recommended" path for developers
- Internal teams competing instead of coordinating
The Root Cause
Snover identifies the real killers:
- Internal politics -- different VPs, different buildings, different roadmaps
- Premature announcements -- declaring direction changes at conferences before products shipped
- Abandoned frameworks -- WPF, Silverlight, UWP all killed by strategic pivots, not technical flaws
- No accountability -- teams that killed frameworks faced no consequences
Why It Matters
- Developer trust is irreparably damaged -- the "Programming Windows" book stopped updating after 2012
- Microsoft's own history proves the tech wasn't the problem -- the management was
- AI era risk -- will Microsoft repeat the same mistakes with AI integration?
← Previous: Huayi Brothers Defaults on 56 Million Yuan Debt, All Founder Shares Frozen as Legendary Film Studio TeetersNext: Iran Ceasefire Mediation Hits Deadlock as Tehran Rejects Islamabad Meeting with US, Qatar Exits →
0