Replies: 6 comments 3 replies
-
|
With 40 bugs getting fixed per year and about 40 work weeks per year, we can say that there's one bug per week that is getting fixed This in turn raises the question: What is the one developer who is fixing the bugs, asctually doing on the other 4 days each week? |
Beta Was this translation helpful? Give feedback.
-
|
Since I'm kind of struggling myself, can you tell me why you shouldn't switch to React, for example, or why you don't do it? |
Beta Was this translation helpful? Give feedback.
-
|
Requirements are MS Store publishing for Xbox and using low-level media APIs, so it had to be a UWP app (due to Xbox) and later it turned out that UWP was too limiting for Desktop targets, which is why we did a WinUI3 version for that, which is largely the same as the UWP app but allows us to do a few things which aren't possible with UWP. |
Beta Was this translation helpful? Give feedback.
-
|
the new Windows Store was written in UWP afaik |
Beta Was this translation helpful? Give feedback.
-
I figured it out: Drawing ASCII art in code comments: microsoft-ui-xaml/dxaml/xcp/dxaml/lib/CueRenderer.cpp Lines 155 to 168 in c8bd154 |
Beta Was this translation helpful? Give feedback.
-
Comparing with MAUIWhen comparing with the fixes in the MAUI changelogs from the past 12 months: WinUI3: 40MAUI: 783That's a factor of 20x Details
|
Beta Was this translation helpful? Give feedback.
-
|
Something to add to the stats: winui3/release/1.4-stable...winui3/release/1.5-stable ( Showing 55 changed files with 1,265 additions and 485 deletions.) The comparison might be wrong because there is |
Beta Was this translation helpful? Give feedback.
-
No, the comparison is correct, I had done a local file diff recently. The changes align with the release notes, that's why I didn't mention it. Given that this diff reflects the changes made over a period of 6 months, it confirms that just minimal work has been done from 1.4 to 1.5. |
Beta Was this translation helpful? Give feedback.
-
|
This is an excellent step towards RFC 9225 compliance! |
Beta Was this translation helpful? Give feedback.
-
It's simple math:
Makes an average of 20.
Releases are scheduled for about every 6 months - means 40 bugs get fixed in a year.
Current open bugs: 677
677 / 40 = 16.925 years
2024 + 17 = 2041
YAY!
But only if everybody would stop reporting any new ones. If we take that into account:
In the past 12 months, 383 (now open) + 313 (now closed) bugs have been created (https://github.com/microsoft/microsoft-ui-xaml/issues?q=is%3Aissue++label%3Abug+sort%3Aupdated-desc++created%3A%3E2023-03-07)
Let's take only the open ones to extrapolate. Assuming that in the coming years, 383 bugs will be filed per year which can't be closed, then the count won't be zero, but instead
6,511 Bugs in 2041
Oh....
Something is going very wrong here, to say the least.
Beta Was this translation helpful? Give feedback.
All reactions