←back to thread

304 points vyrotek | 2 comments | | HN request time: 0s | source
Show context
lpln3452 ◴[] No.45896187[source]
If it runs on Avalonia anyway why choose MAUI? If you have the option just use Avalonia. MAUI is unfinished and its docs is awful.

Do you want to build an app using MAUI? Unless you build an app that barely deviates from the template, expect to desperately search through decade old Xamarin documentation and figure out the details through painful trial and error.

Good luck.

replies(2): >>45896860 #>>45896875 #
1. LeFantome ◴[] No.45896860[source]
They addressed this.

It is a way to get people choosing the "official" path (ie. choosing MAUI) to experience Avalonia. They are hoping you come for the MAUI and stay for the Avalonia and become an Avalonia developer.

As for, why choose the Avalonia version of MAUI, there are three reasons: - Linux support (the big one I think) - Drawn framework (same renderer on all platforms) - WASM support (probably useful sometimes but not the real draw)

They are making a big deal of WASM here because it is easy to demo. We can all go into it and run it. But do we want to use it for our apps?

As for, why not Avalonia directly? To loop back to the beginning, it is because you do not yet know Avalonia and trust it. The Avalonia team is hoping this helps with that.

replies(1): >>45896915 #
2. munchler ◴[] No.45896915[source]
Thank you for explaining this. I didn't even realize this was an Avalonia project until you pointed it out. I like Avalonia (and love .NET in general), but I think the messaging on this needs a lot of work. Avalonia is creating unnecessary cognitive dissonance by emphasizing MAUI, which is a competing project after all.