Enhancing .NET MAUI: Quality Performance and Interoperability in .NET 9 | OD534
Вставка
- Опубліковано 21 тра 2024
- Discover the latest quality improvements, performance enhancements, and interoperability features in .NET MAUI with .NET 9. This session delves into how .NET MAUI has evolved to provide a more robust and performant framework for building cross-platform mobile and desktop applications, emphasizing the improved tooling and developer experience.
To learn more, please check out these resources:
* aka.ms/Build24Collections-Dev...
* dotnet.microsoft.com/en-us/le...
* github.com/dotnet/maui/
𝗦𝗽𝗲𝗮𝗸𝗲𝗿𝘀:
* Maddy Montaquila
* David Ortinau
𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝗜𝗻𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝗼𝗻:
This video is one of many sessions delivered for the Microsoft Build 2024 event. View the full session schedule and learn more about Microsoft Build at build.microsoft.com
OD534 | Developer Tools
#MSBuild - Наука та технологія
I appreciate the presentation. My expectation is to move all mobile apps development to .NET MAUI. I cannot do it right now. I need MVU model without dependencies on paid 3rd parties. MVVM strategically is not an option for my team. But with MVU I would start right away. There were a lot of mouse handling issues, performance problems, iOS/Android multiplatform support model is pretty good, but documentation/samples is almost absent. Copilot helps but not in every situation. WELL DOCUMENTED MAUI library and component support is needed.
Don't forget about lack of Linux support
@@zoiobnu Desktop apps let alone Linux are not a priority for anyone in today's age. Besides MAUI is mobile focused, not really a solid choice for Desktop from what I hear
@@sumomaster5585 this is because we moved to flutter. Maui is multiplatform, so desktop and mobile
Wow so glad you are doing NativeAOT. The mono compiler used in iOS is very clumsy and can’t handle complex generics.
@@gdargdar91 mono was simply moved into the dotnet/runtime repo. No fundamental change here.
@@gdargdar91 it’s still mono
Button demo is fine. But let's add proper design with shadows, picture in a button properly positioned and sized, make it svg, add changing colors when navigating using tabs, implement click, release with changing colors. I bet you will spend a lot of time doing these usual things that you can have in React without any hassle.
MAUI was not intended to be capable of handling more than a button demo. I see this every day. Again and again.
Agreguen componentes por favor
The incompetence of the MAUI team is really fascinating. Delivering a horrible product over and over again, but celebrating it, like they found the cure for cancer.
And every day i ask myself, will we ever get the “live visual tree explorer” with the capability the WPF version had 15 years ago.
Like: inspecting properties, especially bindings.
Is that the only issue you have? That's enough to call them incompetent?
@@RenegadeVile thats just one example of many issues.
The main problems are:
- quality of controls/handlers (and introducing several new controls, while existing controls are broken for years)
- management/prioritization of issues
- minor updates like 8.0.10 > 8.0.20 randomly break
- bad communication/documentation (a lot of things like 'MauiVersion' are not documented properly, it's only mentioned here and there)
Hybrid is amazing. So much faster to develop with
... still betting on .net maui as Alternative for JavaFX ))
Still not even close to replicating the functionality of the technologies it is supposed to replace. It’s very difficult to justify the investment in .NET MAUI when Microsoft themselves don’t seem to be interested in doing so.
This is the framework Microsoft isn't using on their own products like Microsoft Teams, Skype, VS Code, Microsoft Math Mobile, etc, etc. Why I am going to use something the creator don't use for a good reason. yeah, sure !!
After 2 years of working 9 to 5 with Maui, i know why MS isn’t using it for their products.
It’s so fundamentaly flawed, that it’s like trying to empty a river with a bucket. Or fix a cracking dam with patches.
It’s the worst dev experience i had in 13 years, which i spent with a lot of WPF and a few years of angular/react/vue.
And the worst of it all is, that MAUI is 80-90% the exact same source code as Xamarin.Forms, but MS sold it as “the big new thing”.
In essence the framework is more than 10 years old and should be very mature now.
Those products have existed long before MAUI did. It would make no sense to rebuild these apps just because there is a new framework.
The argument of gerald is so unbelievable bad.
1. Microsoft Teams was rewritten, and DESPITE maui has 2 years of GA now, they decided to use react.
2. MAUI is 90% the same as Xamarin.Forms was before (look in git blame, it’s mainly namespace changes). Xamarin and Mono is 99% the as before, though they call it “.Net for android/ios” now
2.b. MAUI is NOT a “new thing”, it’s just Xamarin.Forms 6/7/8/9!
3. MSFT does not use MAUI, cause they didn’t use Xamarin.Forms, cause it’s only an older version of what they call “MAUI” now.
@@jfversluisWhat about all the developers who created apps in Xamarin then? They are forced to 'upgrade' to MAUI which is a lot of work. One rule for Microsoft and another for their developer community?
@@StewSims we have apps that are migrated to MAUI or being migrated currently. And also apps being built with MAUI. We have no different rules internally.
Feels not like allot of maui love at mo typical
Seams that Microsoft has slowed down the investment in MAUI. Seriously how many develoeprs are left working on MAUI?is Microsoft just killing it slowly? Why Microsoft not using it for its own projects? This is what people what to know so they can plan their investment for the future.
There has been no slow down whatsoever.
The point is, the project has ever been extremely low on developers, and apparently had/has zero testers/QA.
It relies mainly on users providing bugfix MRs. The bugfix MRs i‘ve seen from the maui core devs have a bad quality and usually fix only half of the problem and only for one of the three main platforms.