What?
Who asked for this? What problem is it trying to solve? I read the article, but it sounds like any other framework waffling promise.
Microsoft's MAUI (Multi-platform App UI), the official .NET solution for cross-platform desktop and mobile apps, will get Linux and browser support via Avalonia, a third-party framework. MAUI is an evolution of Xamarin Forms, a cross-platform framework for .NET first developed outside Microsoft and acquired in 2016 along with …
People who want to develop cross-platform applications (which is mostly people who used to develop traditional Winforms business applications but don't want necessarily to be dependent on Windows).
Avalonia has actually proved to be reasonably popular while Microsoft has been flailing around, unable to get a grip on its future UI strategy. Given their tardiness and the bitter taste left by the imposition of Windows 11, a more pertinent question might be "what's the point of MAUI?".
Filed a bug on Avalonia over a year ago and it's still open :-( Unfortunately, it's a complete blocker for this project. Luckily, it's a personal project, so more annoying than life threatening. i'm going to look at Uno (https://github.com/unoplatform/uno) which will, no doubt, have a different set of bugs.
The meta-problem with all this is the strong tendency of OS programmers to build mountains of access methods and APIs, of third parties to build frameworks, and of application programmers to wrongly-believe that using these are the The Way to do things programmatically.
It's not a OS-provider-specific thing, and it isn't microcomputer-specific; mainframes and minicomputers have/had their equivalents.
All these (sometimes Jenga-tower-like) mountains of code provide bug-breeding grounds and exploitable flaws.
K.I.S.S.
If I find myself needing to display a video clip and sound from inside a program I'm writing, I'm not going to use the API dejour (Macromind Shockwave, Macromedia Flash, Apple QuickTime, Video for Windows, DirectX version-whatever, Video4Linux, Video4Linux2, etc.).
I will invoke a video player already installed on the system to do that job for me.
It's the programmers default compulsion to write a 'framework'.
I've done it, and am currently trying hard not to do it on a new project I'm working on.
My current thing is: 'Just use the client library.... any abstraction I write will subconciously mirror whatever the 'first' implemenetion is so just use it rather than abstract it....'