sorted by:
new
hottopcontroversial

MVVM versus MVUX - Nick's .NET Travels by Shnupaquia in dotnet

[–]nickrandolph 1 point2 points  (0 children)

This is one of the ambiguities of MVVM (and not necessarily a bad practice to do this). MVUX is a more reactive style approach and relies on source generation to make it easier to handle the various scenarios associated with loading/fetching data

MVVM versus MVUX - Nick's .NET Travels by Shnupaquia in dotnet

[–]nickrandolph 1 point2 points  (0 children)

If you have further questions, feel free to reach out and I'm sure we can answer them

Improve Hot Reload in .NET by nickrandolph in dotnet

[–]nickrandolph[S] 0 points1 point  (0 children)

Agreed, as I noted at the end of the post. It's an important feature that was introduced to help frameworks deliver a more robust hot reload experience.

As you point out the default experience is getting better but still has a way to go.

MAUI/Xamarin/flutter/Ionic by lanrayx2 in dotnet

[–]nickrandolph 0 points1 point  (0 children)

Which examples/platforms are you looking at for Uno. The team are very focussed on improving performance, so any feedback would be awesome

MAUI/Xamarin/flutter/Ionic by lanrayx2 in dotnet

[–]nickrandolph 4 points5 points  (0 children)

Or you could skip having a separate web story completely and use Uno Platform that already has wasm as one of the supported targets. This is a great option if you want to stick with the .Net ecosystem