Live data from Hacker News

.NET MAUI: .NET Multi-Platform App UI

github.com

161–170 of 260 posts

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

#161

Earlier quoted context omitted.

> 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 b…

The fact that you have to interface between different teams/languages is often a big part of the slowdown. The productivity improvements are real. Not having to design and expose an API for the frontend and instead just reuse the same classes and services is a massive shortcut. Running Blazor on the server is even easier because there's no serialization at all and you can directly call database queries in response to…

Then why didn't Meteor take off fully? Because that was the promise of universal JS, about 10 years ago...

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

#162
post #157

.NET 6? Hold up, WPF was never really finished. This is demonstrated by existence of companies which sell lacking components that should otherwise have been included with WPF: Telerik, Infragistics, Syncfusion etc. Heck, creating a Report with out-of-the-box WPF is an unforgettable nightmare. I, for one, would prefer that Microsoft, instead of pumping all these half-finished "cool new toys", ships stable, performant,…

It remains a framework at the end, same as React. The difference is there is less concurrence, and developers can price up their components.

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

#163
post #122

Earlier quoted context omitted.

Ditto, I've no desire at all for web applications--or heaven forbid clients--to poke directly at a database or cache, or otherwise obviate the need for APIs. One will need to deploy, scale, monitor, and secure those things very differently from one another.

We use SQLite for storage of all things. The entire application lives on a single machine. OurApp.exe: SQLite C# Services Razor Components When you have a stack like this, Blazor goes into additional dimensions of productive. Every F5 of the app is a complete stack running without any frustration in setting up databases, containers, message buses, etc. None of the concerns regarding scalability apply when you plan to…

Not familiar with .NET, but am intrigued by the Sqlite all-the-things bit -- can you run your LINQ queries client-side? (e.g. for offline capable apps)

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

#164

Earlier quoted context omitted.

FWIW, this will be supporting Blazor in addition to XAML. So you can have a MAUI app that just handles native hosting etc. and shows your actual UI in a web view. It's admittedly confusing and not all that well explained.

> It's admittedly confusing and not all that well explained. Can anyone help a brother out with a good repo or two that codesplains MAUI decently?

I think you might need to wait for that, MAUI’s still being worked on for the upcoming .NET 6 release.

My understanding (based on talks and blog articles) is that it’s basically Xamarin brought up to speed with .NET 6. So it can use the SDK style projects and other modern .NET+C# features. For UI you’ll be able to use XAML (as before), a new model-view-update paradigm, or Blazor.

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

#165
post #157

.NET 6? Hold up, WPF was never really finished. This is demonstrated by existence of companies which sell lacking components that should otherwise have been included with WPF: Telerik, Infragistics, Syncfusion etc. Heck, creating a Report with out-of-the-box WPF is an unforgettable nightmare. I, for one, would prefer that Microsoft, instead of pumping all these half-finished "cool new toys", ships stable, performant,…

I think that it was intentional. Microsoft often comes under pressure for competing with their suppliers and this was the one example where they didn't even try.

It's also why no-one used WPF: without a grid it was worse than Visual Basic 6 for Microsoft's bread-and-butter business customers. This was a huge strategic misstep, as instead of hiring "WPF" developer you had to hire a "Telerik" or (shudder) "Infragistics" developer or spend a coupe of months extra onboarding new hires.

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

#167

Earlier quoted context omitted.

The fact that you have to interface between different teams/languages is often a big part of the slowdown. The productivity improvements are real. Not having to design and expose an API for the frontend and instead just reuse the same classes and services is a massive shortcut. Running Blazor on the server is even easier because there's no serialization at all and you can directly call database queries in response to…

Then why didn't Meteor take off fully? Because that was the promise of universal JS, about 10 years ago...

Meteor's problems were around performance and features (or the lack of them) IMO, which are not in principle ones that will crop up if you try to unite a stack around a single language.

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

#169

Fool me once shame on you, fool me twice shame on me. Windows phone/Xamarin, Microsoft really doesn’t understand what mobile developers want. What’s the point in investing to learn something when it will be in the hospice next year.

Whats the story with Xamarin now? Does it have a present/future?

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

#170

Fool me once shame on you, fool me twice shame on me. Windows phone/Xamarin, Microsoft really doesn’t understand what mobile developers want. What’s the point in investing to learn something when it will be in the hospice next year.

I stopped counting how many generations of UI Frameworks (Modern UI, UWP, WinUI, ...) they released since Windows 7. All of them ware practically unusable. Some reasons:

  - They only work for the newest Windows Build
  - There are no compatibility packs to target older Windows Versions (7 or 8) or even older Windows 10 Builds (not even the Windows 10 LTSC)
  - They are more proof-of-concepts and feel unfinished. After the release, they only get minor updates
  - All the minor updates need the newest Windows Build again
  - Your customers ask you if you are crazy, because your software doesn't run on a 5 year old PC, that doesn't auto upgrade to the newest Windows version anymore

There are some great alternatives to check out, which even provide cross platform support:

Avalonia: https://avaloniaui.net/

Uno Platform: https://platform.uno/

Post reply on HN