Sonic-Hybrid-Ultimate VS Windows UI Library

https://github.com/CCIGAMES/Sonic-Hybrid-Ultimate most of the context is in the readme file in the repo

https://github.com/CCIGAMES/Sonic-Hybrid-Ultimate I have a project that is a c# mod/extension of the Sonic 1 and 2 mobile remaster engine. Basically it uses/unpacks the data files from Sonic 1, 2 and Sonic CD (which the user has to submit themselves by legally owning the games) And makes it run as one game. This project was made by a guy named Xeeynamo and was extremely bugged. I made a fork around a year ago for safe keeping, occasionally altering the readme for ideas. But now I've entered the stage of actually doing something with it. My plan/project is to fix its bugs and add support for another fan mod/extention called sonic 3 air which is made in c++ like the retro engine (sonic 1, 2 and cd's remaster engine) and is basically like a fancy emulator that translates the source code of sonic 3 to run like a data file on the emulators engine, which again, the user must submit themselves by owning the game. Sonic 3 air support is along way away, So I'm focusing mainly on fixing bugs. And I am a little busy with my final year exams as well as other projects, Plus my low end pc/laptop and a net6 bug the project has are both stopping me from contributing as much as I can All the bug/setup info is in the read me file in the repo

I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.

The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).