Replies: 13 comments 4 replies
|
no |
|
C++/WinRT has been in maintenance mode since March 2023 and it is quite clear from its commit logs that not much has been happening beyond bug fixes, only a few per month, yet they keep talking about using C++ with WinUI it as if there was state of the art tooling. |
|
Itâs not really a team, just some folks who donât have anything else going on. You should check out the previous community calls; different people show up every time. |
|
I swear, MS is like Lucy and Charlie Brown. They yank the football every time (Metro, WinUI2, WinUI3, ad nauseum). I'm really getting sick of it and they're driving me into the arms of Google/Android. I'm still mad at them for killing the Surface Neo. A perfect tool for "walkaround computing". |
|
Wow, telling this has no response... |
|
Mike Crider (@codendone) Michael Hawker (@michael-hawker) Is anyone at MS reading these concerns? |
|
Thanks to those who replied and followed this, but it seems that no real response is coming out of Microsoft. I know there has been other similar posts and links to this post, like this one: What is the status of WinUI? But so far nothing concrete, people will look at it and "we have been working on Build". |
|
Yes, our business is concerned with the lack of progress, enormous amounts of bugs and lack of performance with WinUI, so much so that we're now looking at jumping off. Which is sad, because we believed the platform had promise. The complete and utter lack of transparency and communication is a great concern for us - I'm not going to hold my breath for there to be an official response. |
|
Correct me please if I am wrong. Although you may not see much response and discussion in this project, but actually I see WinUI updates and discussions as part of the MAUI project. This is my understanding - When they improve MAUI for Windows (and other platforms), they are actually improving WinUI isn't it? And I do see a lot work going on under MAUI project and also Windows App SDK (which is again component of WinUI). |
|
Based on what Iâve seen in the past few months, the WASDK team (and Microsoft in general) are mainly focused on adding AI features. For example, the latest versions of WASDK include new Windows AI APIs. Also, most of the talks at MSBuild were about AI. And itâs not just Microsoft, almost every tech company is only talking about AI now. All new research papers are about machine learning and AI models. So, I think weâll have to wait for this AI trend to settle down (maybe months or even years) before we get a clear answer on whether WinUI will continue to be developed or if it will be abandoned. |
|
What we need is transparency and communication, not silence. |
|
Meanwhile Apple and Steam are ripping into them from both sides, releasing more fancy and more effecient frameworks and systems, and Microsoft can't even finish their own framework that they themselves too use, even if their life depended on it. |
|
Always, Azure and AI. |
|
RIP WinUI3, can't think of any other MS project coming back from this state |
|
Think I will bring this up again, on November 5th last year we were told that now things would finally change and now it seems to be radio silence again. So are we back to start again with 0 development or is things still happening? |
|
This thread will give you latest update: #10700 |
|
Thanks, missed the last few replies in there. To those who don't want to read all in there. There is still something happening but they are a bit delayed with phase 3. |
Uh oh!
There was an error while loading. Please reload this page.
Simple question: Is there still a team in Microsoft with the purpose of developing WinUI?
I known some related stuff has been released recently, but based on the last community call and the lack of a follow up to that, the lack of bug fixes (even though somebody is categorizing them) and the lack of core WinUI development, I just have to ask.
All reactions