The project seems old, based on imperative UI. Now, in the declarative UI world, we have SwiftUI for iOS and macOS, Jetpack Compose for Android and desktop, Flutter for mobile, web and desktop, React for the web. Who will invest in a technology still based on xml and imperative code ? The declarative UI works very well, is simpler, is faster to create UI, less code is needed, is simpler to create reusable components, is theme based so simpler to adapt to the changes, are reactive, can have a read-only global state to reduce the complexity. Nowadays all the greenfield projects are web based and mobile base, and it’s rare to create desktop application and, in most of the cases, they are JavaScript web apps (like Visual Studio Core) or web-assembly apps (Figma/Autocad). Come on Microsoft, if you want to create something for the future, please be more bold. And: is Project Reunion compatible with the Fluent design promised 4 years ago and still not used in Windows 10 ?
It should be: Is WinUI 3.0 is aligned with .NET 6? and is WinUI 3 is the version number? So, there is no such as WinUI 3 version 1? I am confused. There is no such .NET 6.1, I believe MS is making sure that there will be no point releases. I think, its best for WinUI 3 to follow that.
Tried WINUI 3. Its still very infantile with quirky issues, and does not even have a designer in VS. Why Microsoft put it out as production-ready is not known.
I like Reunion, seems like one stop shop, kind of like how VB did back in 1999. I worry that packaging UWP with anything is a time sink, because UWP/WinRT should probably never have been born, and it has no real success story. For so many of us, it's existence is annoying/distracting .
I feel the same way about Win32, all this backward compatibility has to stop, can we move forward now pls. The sooner we can just write against the UWP and deploy it how we like, the better.
Thanks! It will be interesting to see more on Build 2021.
is that a geometry dash reference?
get down get up again
You said that winUI is/will be independant from the OS, yet in demo it said that would work from win10.127 build?
The project seems old, based on imperative UI. Now, in the declarative UI world, we have SwiftUI for iOS and macOS, Jetpack Compose for Android and desktop, Flutter for mobile, web and desktop, React for the web. Who will invest in a technology still based on xml and imperative code ? The declarative UI works very well, is simpler, is faster to create UI, less code is needed, is simpler to create reusable components, is theme based so simpler to adapt to the changes, are reactive, can have a read-only global state to reduce the complexity.
Nowadays all the greenfield projects are web based and mobile base, and it’s rare to create desktop application and, in most of the cases, they are JavaScript web apps (like Visual Studio Core) or web-assembly apps (Figma/Autocad). Come on Microsoft, if you want to create something for the future, please be more bold.
And: is Project Reunion compatible with the Fluent design promised 4 years ago and still not used in Windows 10 ?
You said it so well!
Who wants to develop apps in XAML now? 🙄
They need to be bold like Apple.
Please explain the differences Between .Net MAUI and .NET6
I need desktop publishing! So sad it was pushed :(
When WinUI will be support Xamarin?
afaik MAUI (the new version of xamarin) will use WinUI for targetting windows
Man i would love to work for microsoft
It should be: Is WinUI 3.0 is aligned with .NET 6? and is WinUI 3 is the version number? So, there is no such as WinUI 3 version 1? I am confused. There is no such .NET 6.1, I believe MS is making sure that there will be no point releases. I think, its best for WinUI 3 to follow that.
No XAML designer scares the crap out of me!
Tried WINUI 3. Its still very infantile with quirky issues, and does not even have a designer in VS. Why Microsoft put it out as production-ready is not known.
Was I the only one looking for a geometry dash level lmfoa
HELP
I like Reunion, seems like one stop shop, kind of like how VB did back in 1999. I worry that packaging UWP with anything is a time sink, because UWP/WinRT should probably never have been born, and it has no real success story. For so many of us, it's existence is annoying/distracting .
good luck deploy those crappy win32 on ARM at native speed
I feel the same way about Win32, all this backward compatibility has to stop, can we move forward now pls. The sooner we can just write against the UWP and deploy it how we like, the better.