The DARK SECRET Behind Microsoft's Frontend Collapse

RickRick
2 min read

I began my professional journey in 2006, falling deeply in love with C# and becoming a Microsoft enthusiast. Back then, becoming an MVP was like winning an Oscar in the Microsoft ecosystem - it was my dream.

When I discovered WPF, I was captivated by its animation capabilities, 3D graphics handling, and XAML - which I still consider superior to React in many aspects even in 2024. Microsoft's Expression Blend was revolutionary, offering Figma-like fluidity in UI creation that React's ecosystem still struggles to match.

"I decided to bet everything on becoming a frontend developer using WPF, and then Silverlight came along - if you were a XAML developer, you probably adored it as much as I did."

I invested years of my life in these technologies:

  • WPF

  • Silverlight

  • UWP All practically dead by 2024.

I achieved my goal of becoming a Microsoft MVP for 5 consecutive years. The MVP Summit in Redmond was magnificent - back when being an MVP truly meant excellence in your field.

The Downfall:

  • Microsoft abruptly killed Silverlight

  • WPF investment decreased dramatically

  • UWP emerged with severe limitations

  • All focus shifted to Azure (their current golden goose)

Instead of creating a plugin-free Silverlight equivalent to compete with React while maintaining XAML's power, they created Blazor. While Blazor is decent, it's far from React's current capabilities.

Microsoft's frontend technology regression is evident in their confusing array of choices:

  • Win32

  • Windows Forms

  • MAUI (which is problematic)

  • WPF (existing like a zombie without significant updates)

  • WinUI (limited to native MS apps)

  • The confusing Blazor-MAUI combination

Finally, in 2016, I threw in the towel. I haven't used WPF since, and I don't see myself using Blazor or MAUI in the future. Microsoft surrendered the crown to React and other technologies that, ironically, are still primitive compared to what Microsoft had in the 2000s.

Today, I only use ASP.NET Core and Azure from Microsoft's stack - both solid products. But in frontend development, I miss the days of XAML supremacy.

0
Subscribe to my newsletter

Read articles from Rick directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Rick
Rick

15+ years of experience having fun building apps with .NET I began my professional career in 2006, using Microsoft technologies where C# and Windows Forms and WPF were the first technologies I started working with during that time. I had the opportunity to actively participate in the Windows ecosystem as an MVP and Windows 8/Windows Phone application developer from 2013-2018. Throughout my career, I have used Azure as my default cloud platform and have primarily worked with technologies like ASP.NET Core for multiple companies globally across the US, UK, Korea, Japan, and Latin America. I have extensive experience with frameworks such as: ASP.NET Core Microsoft Orleans WPF UWP React with TypeScript Reactive Extensions Blazor I am an entrepreneur, speaker, and love traveling the world. I created this blog to share my experience with new generations and to publish all the technical resources that I had been writing privately, now made public as a contribution to enrich the ecosystem in which I have developed my career.