@29:07 answered my question. No cross platform UI. As a Windows desktop developer of 25 years I see WinUI as just another native UI for Windows. It looks like it offers marginal improvements over WPF and in some ways not a huge improvement over WinForms. It feels like a way of trying to keep UWP alive and I can't really see any incentive to port my application to it. At this time cross platform frameworks such as UNO and QT look more attractive than where Microsoft is heading.
Microsoft will be developing MAUI, which is cross platform for both mobile and desktop. The linux support is unfortunately a community effort. There is also Avalonia (Not owned by Microsoft), if you only care about cross platform for desktop.
@@WorstDeveloper MAUI looks to be "single project" but still multiple codebases within for each platform. Even if it's "single project" you'll still end up having to code specifics for each platform. Microsoft could absolutely nail the cross platform requirement, but they'll fluff it as they usually do.
I haven't tried it, but it sounds like it should be possible to use Blazor+Electron for cross platform. My WinUI hello world is using close to 50MB, so it may even be hard to argue that Electron is too bloated in comparison.
@@EricTViking You're always going to have some platform-specific code for any cross-platform UI framework. If it didn't support platform-specific features, it would only be able to support the lowest common denominator.
@@LimitedWard agreed, but the platform specifics should be very specific to the point of being non-essential for general UI use. Java came very close to achieving the write once run anywhere dream but didn't quite fulfil it.
Can you make your question more clear? The UI implementation is done in C++ but you can code in any language supported by the .NET framework to create Desktop Apps using WinUI 3.
So another UI that solves problems no has. Providing a solution no one asked for. Great work guys wake me up when you have some kind of designer support. The last thing you put out that didnt absolutely tank productivity and quadruple design time was Winforms. In an age where IT budgets are getting thinner and thinner this is just another DOA tech. BTW update your little history of UI to reflect that WPF was so bad that not even MS used it for like the 1st 5 years.
I feel you. But Win32 is just the name for Windows Desktop Apps (I think). It only goes back until Windows 10 Build 1809, so I guess they aren't really carrying bloat before that windows version.
Damn... Before MS finish a tech or clear it with bugs... they release a new one full of bugs and untested... again and again... Damn... Before MS finish a tech or clear it with bugs... they release a new one full of bugs and untested... again and again... Damn... Before MS finish a tech or clear it with bugs... they release a new one full of bugs and untested... again and again...
That was an excellent talk!
A quick question: At this time, which one should we use to create modern native apps?
WinUI or MAUI?
And now all of us know that UWP is obsolete.
Excellent presentation
Glad you got the information you needed from it!
just show me where i can create a button dammit!!!
In Xaml...?
@29:07 answered my question. No cross platform UI. As a Windows desktop developer of 25 years I see WinUI as just another native UI for Windows. It looks like it offers marginal improvements over WPF and in some ways not a huge improvement over WinForms. It feels like a way of trying to keep UWP alive and I can't really see any incentive to port my application to it. At this time cross platform frameworks such as UNO and QT look more attractive than where Microsoft is heading.
Microsoft will be developing MAUI, which is cross platform for both mobile and desktop. The linux support is unfortunately a community effort.
There is also Avalonia (Not owned by Microsoft), if you only care about cross platform for desktop.
@@WorstDeveloper MAUI looks to be "single project" but still multiple codebases within for each platform. Even if it's "single project" you'll still end up having to code specifics for each platform. Microsoft could absolutely nail the cross platform requirement, but they'll fluff it as they usually do.
I haven't tried it, but it sounds like it should be possible to use Blazor+Electron for cross platform. My WinUI hello world is using close to 50MB, so it may even be hard to argue that Electron is too bloated in comparison.
@@EricTViking You're always going to have some platform-specific code for any cross-platform UI framework. If it didn't support platform-specific features, it would only be able to support the lowest common denominator.
@@LimitedWard agreed, but the platform specifics should be very specific to the point of being non-essential for general UI use. Java came very close to achieving the write once run anywhere dream but didn't quite fulfil it.
Niet i will use this on the hmi on our machine
WinUI + UNO looks promissing!
does it cannibalize xamarin ?
@@wi8shad0w .NET MAUI enters the chat
@@caret4812 and exits
Why not .NET Native for Desktop Apps? :(
Can you make your question more clear?
The UI implementation is done in C++ but you can code in any language supported by the .NET framework to create Desktop Apps using WinUI 3.
So another UI that solves problems no has. Providing a solution no one asked for. Great work guys wake me up when you have some kind of designer support. The last thing you put out that didnt absolutely tank productivity and quadruple design time was Winforms. In an age where IT budgets are getting thinner and thinner this is just another DOA tech. BTW update your little history of UI to reflect that WPF was so bad that not even MS used it for like the 1st 5 years.
Why can't Microsoft leave behind the legacy bloat and focus on future developments? Win32?
I think Windows RT was that attempt. But the enterprise industry backbone is heavily reliant on Win32 until developers are forced to shift to UWP.
because millions or billions of devices over the world are not upgrading
and still using win7, or even winxp .
1000000000s of softwares,tools and utilities are based on win32
So yeah legacy support and backwards compatibility is what people use Windows for
I feel you.
But Win32 is just the name for Windows Desktop Apps (I think). It only goes back until Windows 10 Build 1809, so I guess they aren't really carrying bloat before that windows version.
Damn... Before MS finish a tech or clear it with bugs... they release a new one full of bugs and untested... again and again...
Damn... Before MS finish a tech or clear it with bugs... they release a new one full of bugs and untested... again and again...
Damn... Before MS finish a tech or clear it with bugs... they release a new one full of bugs and untested... again and again...