From a quick look, I can't find a reason. why? Even MS doesn't fully believe in Maui, as it seems they reblessed WPF. For Avalonia to do the work of MS seems weird, their own free regular WPF-like Avalonia UI toolkit is already the standard for cross desktop development.

I was looking for the line: Microsoft sponsored us. Even then I would not understand why they would spend effort on a doomed project. I know Avalonia being a small company has a big task ahead of porting Avalonia UI to Wayland, which makes porting MS semi-abandonware all the more confusing.

But since these people aren't idiots, I gladly assume I am missing something.

▲

corstian 36 minutes ago | parent | next [-]

Between MAUI and Avalonia, Avalonia is the superior framework when it comes to technical quality as well as community response. What Avalonia doesn't have is the enterprise component libraries MAUI has. As part of this move Avalonia is about to reel in these libraries, as well as a whole bunch of MAUI teams.

In other words; Avalonia is coming for MAUIs turf.

▲

siwatanejo 2 hours ago | parent | prev | next [-]

> Even MS doesn't fully believe in Maui

Source: I made it up.

▲

exceptione an hour ago | parent | next [-]

MS has multiple personalities, so some might do, I will give you that. Meanwhile, WPF is getting rehabilitated. It seems like that not only the average developer has concluded that all the other UI frameworks since wpf are half-baked. Someone more involved than me makes the same assessment: https://news.ycombinator.com/item?id=47480056

I recommend everyone to ignore all experiments, and go straight for AvaloniaUI, as it is quite similar to wpf, actively devloped and cross-platform. The only downside I see is that Wayland is still in progress yet.

▲

nobodyandproud an hour ago | parent | prev [-]

How many MS products are dog fooding Maui?

When COM rolled out, every product was very much on board.

The need for Maui in-house is for…what?

	▲	skeeter2020 an hour ago \| parent [-]
		doesn't look like much; the seem to use electron for almost everything in this space. If they had faith in Maui something (VS Code, Teams, Outlook, ... calculator?) would use it.

▲

nobodyandproud 2 hours ago | parent | prev [-]

> But since these people aren't idiots, I gladly assume I am missing something.

Microsoft politics. Someone who’s aware please confirm but I want to say it’s something like…

Different orgs jockey for power and you can see when the wrong orgs and initiatives influence different products.

What I can’t tell is whether it’s established teams scrambling to stay relevant. Or if it’s new teams and products imposing their influence where they shouldn’t.

But the Windows team doesn’t want to see Linux get traction, so they’ll do their part to hamper any OS shims or any native-first functions in Office.

The Office org wants to expand beyond Windows but for political reasons, the only add-in tech without platform lock-in is JS so they ally with the Azure/Cloud team to allow third parties to create add-ins.

Because of this partnership, rather than making a streamlined add-in store, publishers are required to learn the full complexities of Entra and the Partner centers.

I imagine the UX and .NET orgs are caught in similar political battles; but without any direct income or product to influence.

If I had to guess, they were in the Windows team at one point; but with the platform-independent initiatives (good) it’s been a shitshow over the past 20+ years for desktop developers (bad).

	▲	exceptione an hour ago \| parent [-]
		I agree that MS has often internal conflicts of interest. But that still leaves su with the question: why would Avalalonia do the work that MS did not bother to do, where is the benefit? I mean, Avalonia has AvaloniaUI already.