The client requested a new screen with many details. I informed them that it would take a bit longer than usual, but when I tried to deploy the graphical interface in Visual Studio 2022, I encountered an unexpected obstacle: Windows 11 is mandatory for this task.
Sure, I could manually modify XAML, but coming from Windows Forms, I never got used to designing UI without visual tools—something I envy from my Delphi colleagues.
But this leads me to a deeper reflection: 👉 Why is Windows 11 forcing me to change my hardware? 👉 Do I really need TPM 2.0, or could Windows secure itself without this requirement?
My PC failed the TPM test since it only has version 1.2, and although I don’t fully understand the technical reasons, it seems Microsoft has decided that my system is no longer secure enough for its new OS.
The Cost of Forced Migration
The reality is that now I have to allocate part of my next payment to evaluating a new PC purchase. Not because my current hardware is outdated, but because Windows 11 has imposed a technical barrier that forces me to upgrade.
What's frustrating is that Microsoft hasn’t provided a clear justification for why this change is absolutely necessary.
A Loyal Developer, But Concerned
I love Visual Studio Code and Visual Studio 2022. From its early days in MS-DOS, when it was barely noticed, to its launch as Visual Basic 3, it has been a fundamental tool in my career.
However, I worry that despite its excellence, Microsoft does not inform its followers in advance about upcoming changes or the maturity of its new technologies.
Does Microsoft Only Care About High-End Developers?
Perhaps Microsoft only focuses on its top-tier developers, those with large budgets and resources. But I have to fight every day for my market, where GNU/Linux has lowered my income, and public sector employees often reject proprietary tools.
For years, Windows and .NET have been essential for my work, but now I’m being forced to consider alternatives, such as Rad Studio, which offers a free one-year license with full access to its tools.
What’s Going on with WinUI 3?
I would love to use WinUI 3 for my clients, but it doesn’t even include something as basic as a DataGrid, and its visual controls are not like Windows Forms, forcing me to manually write everything in XAML.
So, is Microsoft really providing tools for the future, or is it pushing me towards alternatives? 🤔
Conclusion: Migration or Imposition?
This is not just a technical issue—it’s about surviving in what we love doing.
The question remains: Is Microsoft considering its loyal developers, or is it simply forcing us to change without thinking about the real costs and impact on our businesses?
Top comments (0)