I do share your skepticism of Microsoft, but it looks like the economics and cash flow dynamics have changed drastically after the advent of the cloud.
Microsoft is more focused on getting developers onto its ecosystem and help them with open source projects with the hope that they will use its Azure cloud services and bring in the money.
My skepticism is a bit relaxed now and I have no qualms using .NET.
It isn't about whether it is open source or not. It's about what will be their stance on GUIs in a year or two and whether the projects of today are abandonded or not. Windows Forms, Silverlight, WPF, UWP, WinUI, Blazor, and then Xamarin Forms and MAUI, and then the third party ones like Avalonia and Uno Platform.
It's insane because actually all anyone wants is Windows Forms and WPF. If Microsoft made a cross-platform version of Windows Forms and WPF, they would be the cross-platform frameworks, at least for desktop.
If you want cross-platform WPF, there is Avalonia. For many normal-ish applications you basically change a few namespaces and that should be bulk of the work to migrate.
I do wonder sometimes whether MS should just pick it up as a default-endorsed desktop UI toolkit for .NET, but I guess rivalries, internal turf wars and other priorities make that difficult.
I love the fact that .NET and friends are open source, but my issue isn't with the licensing, it's with m$ funneling tons of resources on projects that (most likely) will end up being a dead end.
I'd also love if maui actually takes off since it does seem pretty neat, but until microsoft uses it for teams or any other of their clients, I'll pass.
They also aren't even targeting linux or web browsers, which doesn't really make this more compelling than Flutter.
.NET is used all over the place in Microsoft, including many Microsoft Teams services being migrated to .NET. Teams is listed on Microsoft’s .NET customers page.
The commenter was referring to Microsoft's GUI frameworks on offer in .NET and not .NET in general. Of course .NET is used everywhere at Microsoft. C# is one of the most popular languages in the world.
They were talking about Microsoft constantly re-inventing GUI frameworks and then abandoning them. For example, you bring up Teams, but Teams is actually an Electron app, which gets to the point of the commenter.
Actually they moved onto UWP, then they moved onto WinUI 3. Now all this talk about MAUI but they have done zero dogfooding of it. People are sceptical of WinUI 3 but at least they used it in Windows 11.
There's like... zero momentum behind MAUI. The wider industry has learned their lesson and nobody in their right mind would ever use MAUI for a new GUI project unless Microsoft converts 80% of their applications to it.
The only decent GUI framework for Windows is Electron, which is based on Chromium.
Microsoft's new GUI applications use Electron: VS Code, Azure Data Studio, etc...
In other words: Google makes the best Microsoft Windows GUI framework, as endorsed by Microsoft's own developers.
You're talking about momentum within Microsoft, I assume? There's no detectable momentum in the community at large. The ball hasn't even begun to roll. I have not heard or seen anyone using MAUI for anything serious so far. I've been writing Windows applications for 25 years at this point and am certainly not considering MAUI any time soon. They only just added keyboard accelerators--this is obviously not serious yet. To this day we are still writing Windows Forms applications. I'd consider embedding Blazor before I'd consider MAUI.
Having lived through a lot of Microsoft GUI frameworks, I would say that I won't be fooled this easily. Not with another half-assed unfinished library. I'll be interested once it qualifies as whole-assed and not a moment sooner.
And how confident are you that my choice isn't going to be deprecated in a couple of years? I'm not certain that "momentum" is worth much from a company who changes UI frameworks as often as some people change underwear...
I wonder why this is. Is it because management is asleep at the wheel? Is it because teams competes with each other without direction from the top? Is it because heavy rotation of leadership who doesnt know better?
I'm not entirely sure. SkiaSharp is the driver behind all the 2D graphics, isn't it? But the SkiaSharp repo is effectively unmaintained except maybe to support critical things for MAUI.
SkiaSharp has some MAUI integration, but AFAIK it's not used to render things. At least not when I last looked. On most (all?) platforms native drawing methods are used (which fits well into how MAUI works on each platform, admittedly). This comes with the drawback that performance varies wildly across platforms, however. (NB: I've last looked deeply into MAUI about a year ago, so things may have changed.)
https://github.com/dotnet/maui
.NET is Open Source
https://dotnet.microsoft.com/en-us/platform/open-source
I do share your skepticism of Microsoft, but it looks like the economics and cash flow dynamics have changed drastically after the advent of the cloud.
Microsoft is more focused on getting developers onto its ecosystem and help them with open source projects with the hope that they will use its Azure cloud services and bring in the money.
My skepticism is a bit relaxed now and I have no qualms using .NET.
I hope I am not wrong.