Live data from Hacker News

.NET MAUI: .NET Multi-Platform App UI

github.com

51–60 of 260 posts

Re: .NET MAUI: .NET Multi-Platform App UI

#52

How likely will it be that F# is supported out of the box? I understand that this is a push for mobile but hopefully a linux support will be considered. https://github.com/jsuarezruiz/forms-gtk-progress/issues/31

+1. F# deserves a lot more love

F# seems to get love and recognition through C# slowly evolving and absorbing features that have been the F# advantage for a long time (fingers crossed for C# discriminated unions...)

Re: .NET MAUI: .NET Multi-Platform App UI

#53
post #37

The amount of energy Microsoft is pouring into these front-end efforts is pretty incredible. A more recent development that has me very excited is Blazor Desktop: https://medium.com/young-coder/blazor-desktop-the-electron-f... > This leads to the second difference — in a Blazor Desktop app hosted in WebWindow, there’s no built-in web server. Instead, it’s pure .NET all the way down. And while we haven’t seen exactly…

> I have been able to implement things in 4 hours that would easily have taken 4 weeks if I had to argue with other developers about the shape of a JSON blob on the wire.

I can’t comment on your specific circumstances because I don’t know the details, but this reads like someone who is drinking the blazer coolaid.

It’s a technology like any other, with specific trade offs.

If you have a front end team who lacks the basic competence to do something that takes four hours in blazor in less than 4 weeks, then maybe it’s a good trade off.

...but in most cases, for most people, that won’t be the case.

It’s also quite slow, hard to integrate with existing js technology (ie bridge) and very difficult to debug production issues with in my experience.

Re: .NET MAUI: .NET Multi-Platform App UI

#54
post #2

Any direct experiences using this? I've been looking for a good multiplatform UI for desktop that does Mac/Linux/Windows. Mobile is a nice side benefit. It would be nice to use C# again No, I'm not interested in Electron. Blegh.

Have you looked Flutter? It is mobile-first, but does native desktop applications as well. Very battle tested and natively compiled fast code.

Doesn't use native controls

Re: .NET MAUI: .NET Multi-Platform App UI

#55

> In addition, we are enabling developers to write fluent C# UI and implement the increasingly popular Model-View-Update (MVU) pattern. MVU promotes a one-way flow of data and state management, as well as a code-first development experience that rapidly updates the UI by applying only the changes necessary. I am very interested in this. Last year I developed a .Net Win UI/UWP app and while I enjoyed the rich library…

You can try to use Comet [1] today if you don't want to wait for MAUI

[1] - https://github.com/dotnet/Comet

Re: .NET MAUI: .NET Multi-Platform App UI

#56
post #9

Earlier quoted context omitted.

Xamarin Forms was not good tech.... :-)

That's why it exploded in popularity then? Literally exploded and was releasing on a rapid cadence to a fervorous developer base. The current non-MAUI Xamarin is very refined and complete from a performance and feature perspective. It is literally the only viable serious cross-platform and mobile development platform.

Its important to distinguish between Xamarin.Forms and Xamarin.Native (which Forms is built on top of). Xamarin.Native is quite nice and is the best abstraction available today (in my opinion). Xamarin.Forms is indeed not great. It is an OK solution for a subset of problems, but even for those I'm left wondering if the pain is worth it rather than rolling my own native frontends in Xamarin.Native.

Re: .NET MAUI: .NET Multi-Platform App UI

#57

How likely will it be that F# is supported out of the box? I understand that this is a push for mobile but hopefully a linux support will be considered. https://github.com/jsuarezruiz/forms-gtk-progress/issues/31

F# examples:

https://github.com/dotnet/net6-mobile-samples/tree/main/fsha...

Re: .NET MAUI: .NET Multi-Platform App UI

#60
post #23
post #9

Earlier quoted context omitted.

Xamarin Forms was not good tech.... :-)

Hopefully a chance for them to take what they learned through years of experience and cut away from the cruft/technical debt that built up with Xamarin.Forms. I think there is potential for redemption here -- although I do worry the native widget binding approach still comes with a lot of friction that adds unavoidable complexity. However, Maui's new "handler" pattern for native widgets seems like it could be adapted…

I'd love if this could be a step forward but from my fly-on-the-wall perspective following the github, I'm not optimistic that the team has internalized what exactly this new thing should be, and how it should differ from Xamarin.

I'm hopeful though.

Post reply on HN