<story><title>Performance Improvements in .NET 6</title><url>https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-6/</url></story><parent_chain></parent_chain><comment><author>smackeyacky</author><text>I&amp;#x27;m going to pile in too late and sing the virtues of .NET core or whatever its called now.  Deployment of web apps to containers is a breeze, the language is modern feeling.  Roslyn is about the most awesome thing I have played with.  Razor pages are a breeze compared to the giant piles of dependency hell that client side SPAs or node have become.  It feels lean and mean and I can be sitting at a debian box or a windows laptop and the experience in VSCode is identical including deploying code to production on AWS.&lt;p&gt;But like everybody has said, the desktop UI story is garbage.  Fingers crossed Maui turns out to be useful because winforms and UWP are hot garbage. Such a shame from the guys who revolutionised gui development with Visual Basic.</text></comment>
<story><title>Performance Improvements in .NET 6</title><url>https://devblogs.microsoft.com/dotnet/performance-improvements-in-net-6/</url></story><parent_chain></parent_chain><comment><author>foepys</author><text>WinForms and its Visual Studio designer are still broken, WPF is still riddled with bugs and was declared obsolete in ~2017 in favor of UWP, UWP is marked obsolete in favor of WinUI, and WinUI&amp;#x27;s OSS release was postponed just two days ago because it&amp;#x27;s not ready.&lt;p&gt;Microsoft is marketing .NET 6 as the replacement for .NET Framework but you still cannot properly do desktop UI with it. I honestly don&amp;#x27;t understand why they are pushing more and more features when they cannot complete the ones they started years ago. Not to mention that porting WinForms from .NET Framework to .NET 6 requires a rewrite for anything more complex than a Hello World.</text></comment>