Replies: 49 comments 374 replies
-
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one. Thank you! Closed similar issues:
|
Beta Was this translation helpful? Give feedback.
-
Component Vendor Support for WinUI3All the component vendors already know it. TelerikThe two "under review" haven't been updated since about a year. Ref: https://feedback.telerik.com/winui SyncfusionThe WinUI roadmap for 2024 includes only improvements to shared components (i.e. improvements are made for multiple platforms) but nothing specific to WinUI3 controls. Ref: https://www.syncfusion.com/products/roadmap/winui-controls DevExpressThey are explicitly stating that their WinUI3 components are dead: Ref: https://supportcenter.devexpress.com/ticket/details/t1206625/winui-3-the-roadmap-in-2024 |
Beta Was this translation helpful? Give feedback.
-
ConsequencesIf this turns out to be true, this would be a severe incident: 1. You owe me two days of workFor creating the Pull Requests, since I didn't know that they'll be never even looked at due the product being abandonded. Same goes for the effort that so many people have taken in order to submit bug reports or create design proposals. 2. Have Microsoft Representatives been Lying to the Developer Community?This needs to be evaluated. Behaving as if all would be fine and the product would be continued is quite close already. And I recall statements like "all developers are working on WinUI3 now" which I think were made after 2022 and after stopping development (largely), When the UWP bugs were all closed, it was promised that issues will be better handled in the future and it won't happen again. |
Beta Was this translation helpful? Give feedback.
-
I don't think so, it looks like a technical reorganization, nothing is brand new (uwp equivalent). Apart from the fact that I can't figure out why the designer isn't being offered, but it's very much trending the blazor of the dotnet community looks like it's going to win this one. |
Beta Was this translation helpful? Give feedback.
-
WinUI is mismanaged and woefully understaffed. I wrote a post up a while ago which got a lot of traction. Either close this repo and make it internal only and pretend that it's under active development or put it out of its misery. I love WinUI and it had great potential and traction but all good will has been lost by the lack of comms out of Redmond. Remember as well this whole UI framework and stack (WinRT) is as old as Windows 8. DPs of Win8 were available in 2010 or 2011. That makes the tech at least 13 years old. Appalling when you consider how much Android and iOS have iterated over that time. |
Beta Was this translation helpful? Give feedback.
-
My suspicion is that they have pulled off the majority of developers to work on something new. Maybe they'll call it WinUI4 to make the whole story not appear even worse than it does already, but it must be on a very different technical basis. If it was a continuation only, they could have backported fixes and wouldn't have to invest into Xaml Islands. Also the component vendors wouldn't have had to pull their efforts if it wasn't something technically different that is coming. And it's clear that something must be coming: the framework gap on Xbox needs to be filled. App development for xbox is not abandoned, WebView2 for Xbox has just been released in November and UWP is been given up, so there's an obvious gap as Xbox is meant to stay. |
Beta Was this translation helpful? Give feedback.
-
Also the fact that they even converted this serious issue to a discussion to show us how much they don't care: #9154 ...Or at least they don't care that this UI framework is only usable for simple mobile-like apps and don't care that it's unusable for any complex business application. I seriously doubt that something like Visual Studio could be made with WinUI 3, so it's not a replacement for WPF. |
Beta Was this translation helpful? Give feedback.
-
PredictionWhenever they will respond to this, directly or indirectly, one of the first statements will of course be saying that WinUI3 is not dead and will continue to be supported till the end of days (or at least according to the OS support periods). (Yet, that's what I mean by saying that it's dead) NoteI have no insider information on this subject. If I had (like at some occasions in the past), I wouldn't post about it. It's solely based on observation, inference and deduction (and experience from similar cases). There's a chance that I could be wrong, but I don't think so. |
Beta Was this translation helpful? Give feedback.
-
Unfortunately I think you're right. I just really hope they don't go the web route, even for native apps. But even if they don't, the fact that they're creating yet another UI framework/application model is just... They keep making new and new ones and then replacing them with new ones just 3 years later, and those who invested in the previous technology are s*** out of luck. First (that I remember) Windows Forms, then WPF, then Silverlight, then Windows Phone + Windows 8, then UWP, then WinUI 3… all incompatible with the previous ones. Oh and in parallel, Xamarin and then MAUI. I’m afraid it’s going to happen again to WinUI 3… And then Microsoft says that they "care about compatibility".... while leaving developers who are stuck on the previous thing behind. This isn’t how to treat your developers well, Microsoft… Can’t they for once stick to a single framework and work on making it the best it can be, and making the developer experience the best it can be? |
Beta Was this translation helpful? Give feedback.
-
I should mention that the WPF team has recently been activated and is providing WinUI 3 styles and controls.
Also, I must mention that there have been good changes since wasdk v1.5 and we will have good changes in 1.6. |
Beta Was this translation helpful? Give feedback.
-
What's the point of this post? Don't think anything meaningful would come out of this. WASDK 1.5 and 1.5.1 was just out. Community call on 1.6 roadmap is posted. Are you some kind of PR guy to sabotage WinUI just to advertise WPF? |
Beta Was this translation helpful? Give feedback.
-
I feel the slowdown in WinUI 3 fixes and new features is because WinUI 3 is also the Windows component of MAUI. So in this process many bug fixes get postponed and new features/fixes are delayed due to the testing cycle on all platforms. Plus of course the most important is the compatibility between the management of these teams. |
Beta Was this translation helpful? Give feedback.
-
Hello everyone, Mik from Windows team is here, thanks for starting the conversation. Now, it's obviously our platform is not in the place we want to be in the future - there is a big backlog of items that we need to triage and prioritize among different internal and external customers. One of the strongest feedback items we've heard consistently that Microsoft is not using the same technologies we are recommending to developers, and we are working on that too. I think one other area your feedback attributes directly is that our platform is not fully open sourced, we make source code available, but there is not currently a way for community to directly contribute to the release. You can watch the discussion about this topic during our latest WinUI Community Call with specific details. We continue to invest in frameworks Windows developers use. For example, we've recently shared our refreshed roadmap for WPF on GitHub - https://github.com/dotnet/wpf/blob/main/roadmap.md Windows will continue to be an open platform for developers. |
Beta Was this translation helpful? Give feedback.
-
I'm interest in WinUI for about 3 years. But I don't see any advantage compare to WPF yet. |
Beta Was this translation helpful? Give feedback.
-
Oops.. Not dead :o Check out the community call here.. https://github.com/microsoft/microsoft-ui-xaml/discussions/9946 for for more upcoming improvements.. |
Beta Was this translation helpful? Give feedback.
-
Reading this is depressing. Not because I care specifically about WinUI or whatever, but just the state of desktop UI has become such a mess. And it seems like the only things we're seeing from MS are platitudes. I have an editor in my project, and that editor makes use of Now, you're probably thinking "Why not use WPF or Avalonia or etc...". The integration of WPF and Avalonia with my swap chains is a pain (I know, I've done it). And they lock me to 60 FPS, so I can't slow it down or speed it up as I'd like. I can't speak to the ability UWP or WinUI for swap chain integration, but if it's as complicated as WPF or Avalonia, then it's a non starter. Also if the basic components I need are not available (this is an open source project, I can't use DevExpress or ComponentOne to fill the gaps), then I'm out of luck and back to Windows Forms I go. I would just like a focused, and complete UI (at least as complete as Winforms) solution to work with. I want to be able to hook in a swap chain as easily as I can with a Windows Forms application and without any potential airspace issues. And I especially don't want to be spending my time writing controls in XAML that should have been there in the first place (I've experienced this with UWP and WPF - but that was admittedly a long while back). I know my use case is not important or common, but I just feel like everyone only thinks of LOB apps and those of use who do specialized things are kind of forgotten about. |
Beta Was this translation helpful? Give feedback.
-
Please note my new proposal to improve WinUI3 interoperability with other win32 components: #10050 |
Beta Was this translation helpful? Give feedback.
-
@softworkz Also I did not like the whole discussion tone, making it seem that WinUI 3 is a disaster and shame. I think MS devs deserve some respect for their job and dedication with such limited resources. @gitmixen |
Beta Was this translation helpful? Give feedback.
-
Damn. So MS tells you WinUI is the future, you bet on WinUI and then if you find something wrong with it (like, let's say the input validation support or the designer)... it is your fault that WinUI is not that good? I guess now we know why teams at MS are picking Electron over WinUI. |
Beta Was this translation helpful? Give feedback.
-
Why is it so hard for MS to develop a useable UI framework? |
Beta Was this translation helpful? Give feedback.
-
xaml is shit! |
Beta Was this translation helpful? Give feedback.
-
Looking at the broader tech landscape. What has gained in popularity the past few years?
Related question: What is the single most important target platform? Which of the above DON'T support Web browser? Microsoft's apparent answer:
Looks to me like Blazor is Microsoft's "true" cross-platform answer. To me, that is a loss of decades of maturation of what makes a GUI framework "good". Especially since there are two open-source .Net-based GUI frameworks that have been shown running under WASM in browser:
I don't have an opinion on how well those run in WASM. But surely Microsoft has sufficient development muscle to examine all the existing options, and come up with a strong, well-designed, competitor to Flutter. Or port Flutter to .Net 9 and C#? ... I realize none of the above addresses the role of some "native" UI for future Windows OS. Is it practical for an OS to not have a "native" GUI? Or to put it differently, can an OS embrace one or more highly popular cross-platform GUIs, and make that (those) run really well? I don't see Microsoft winning this competition with their own technology. Probably should adapt .Net into a Rust-based technology also. I can dream... |
Beta Was this translation helpful? Give feedback.
-
I actually find it terrifying that this post still has the needs-triage label and has not received even one official response from a member of the team. |
Beta Was this translation helpful? Give feedback.
-
M$ seems to be not cared with WinUI 3 anymore hence the bug causing XAML autocomplete to stop working is still here. Meanwhile, .NET Maui never has this problem |
Beta Was this translation helpful? Give feedback.
-
What junk is this WinUI3? Why not continuing WinUI2 which is WinRT and removing the sandboxing part? I produce compilers on linux for windows. I compile Windows applications to run in Wine using Clang and GCC on Linux. .NET and sandboxing are never viable options for me. Microsoft seems to be undermining Windows with C#. I don’t use Visual Studio, don’t need it, and have no intention of ever using it. Forcing packaging for a walled garden is detrimental to Windows. Why would anyone choose sandboxed Windows applications when they could simply buy a $40 Android phone from Walmart? There’s no reason to use Windows if it’s sandboxed. Why C++ is gated with nuget .net junk? Microsoft's .net is completely failure. Considering Microsoft is bitching on C++ for all their issues, then why not just stop the junk which is Visual C++? There is no reason to use msvc when clang is available. What's the point of WinUI3 when you can just go fix WinRT? WinUI3 is just another attempt to kill computing freedom. I won't be shocked Microsoft will block .exe and other operating systems on PCs for running in the future. If so I would just move to android phones and never come back. https://github.com/trcrsired/llvm-releases/releases |
Beta Was this translation helpful? Give feedback.
-
I do not think microsoft understands why people use Windows in the first place. It is not because of some shit like Recall or Sandboxing Walled Garden junk. (In fact Microsoft's AI did so poorly that even the Wall Street butts against it and that is why Microsoft stock crashed to dust recently) People use windows because it is an open platform that allows changing operating systems and running .exe without all the walled garden and sandboxing junk. If I want sandbox, why can't I use Android, Chromebook, and iPad? They have sandboxed apps, while Windows does not have sandboxed apps. People use it because the most portable abis are Win32 ABIs, and it is the most stable even on Linux. Still, Microsoft totally fked its own platform in the shit excuses of "security" or "all our security issues are .exe's fault or C++'s fault." The most secure devices are useless. MSFT simply does a poor job on security. Of course, Microsoft wants to lock your computer down in the walled garden with App Store junk like apple does. Look at what disaster is of Windows 10/11 S mode? It is just laughable that my $39.99 sandbox phone from Walmart can compile and run Windows on Arm .exe natively while $1000 Win phone or Surface RT back then could not, despite Android being also sandboxed. No wonder Windows on Arm has such a low adoption rate: Microsoft forces the junk, which is Visual Studio, to C++. Please give up MSVC and work on Rust if you guys hate C++ so much. I am thrilled MSVC (cl.exe) dies tomorrow. It needs to die.
C# and Java literally become "native" languages when they cannot work on Android and iOS since they need to compile the runtime, which is why net Maui, Flutters, and many other "cross-platform frameworks" have the wrong idea in the first place. Languages like C++ and Rust can simply compile to things like Wasm to become virtual machine languages. The most portable technique solutions that are most widely used are Web and running windows .exe with wine. Do you see a reason for that? |
Beta Was this translation helpful? Give feedback.
-
Just show an example of winrt without all the xaml, C# and .net junk No more nuget. No build system. No visual studio. No MSVC. No clang-cl junk. Not even Need Windows. Only clang. |
Beta Was this translation helpful? Give feedback.
-
Yesterday I made a post (Great News: All Bugs Will be Fixed In the Year 2041) which was meant to be a somewhat funny complaint about the lack of activity in terms of development progress and dealing with user issues submitted here.
Then I made a comparison of activity between WinUI3 and MAUI and those figures are quite revealing when thinking about it:
How can it be possible that MS is investing 20 times more effort into MAUI than into WinUI3 - the new and designated primary UI technology for Windows desktop?
Simple answer: It can't. It can only be possible in case when WinUI3 is no longer the "designated primary UI technology for Windows desktop".
Now I'm shocked to realize that it's way more serious than I thought as so many details suddenly fit together and make sense when being viewed in the light of that premise.
It all fits together
Smaller Bits
Xbox Development
=> but Xbox is not dead. So the must be something for Xbox which is not WinUI3
Cpp/WinRT in Maintenance Mode
as noted by @pjmlp (thanks!):
Component Vendors
DevExpress are offering a few free components but these haven't been updated since mid-2022.
Their blog entries about WinUI3 stopped in mid-2022 as well (https://search.devexpress.com/?m=Web&q=winui3)
They probably know already about the end of WinUI3.
Timely Coincidence
Wasn't it at the same time (2022) that WinUI3 development had started to be driven down?
XAML Islands as a WinUI3 Exit Strategy
When looking at the changes that were made during the past year, then there's only one area where significant work has been put into: XAML Islands. Even though it had been requested by users earlier, it's not a most-wanted feature, but still, MS picked exactly that part as the one major subject of work.
XAML Islands allows to integrate WinUI3 content as "islands" when using other UI frameworks. Why is this so important? Who needs this other than a few with very specific use cases?
When customers want to modernize their applications, who would start by implementing something in WinUI3 which is then shown like a control/window within a WPF or WinForms app? Normally, such migrations would rather go the other way round: starting with a new application framework and subsequently migrating legacy components. But that's what is not being worked: There's nothing like a hWnd-Panel (which had also been requested by users).
Bottom line: When establishing a new framework for app development, then it's usually crucial to provide ways for developers to integrate legacy components into the new framewrok to allow subsequent migration, but not the other way round. Provisioning for the other direction only (and also as the only major change) can only mean that this is the end of the road for WinUI3, and XAML Islands are just implemented to soften the impact for affected developers enabling a life-after-death existence for WinUI3 components.
MS, when did you plan to make the RIP announcement?
And what will be the replacement?
Beta Was this translation helpful? Give feedback.
All reactions