yasb VS Windows UI Library

What an absolute mess. In the meantime I'm glad to have seen alternatives like yasb[1] popping up.

[1]: https://github.com/denBot/yasb

You can use yasb to show a status bar, similar to polybar. Follow instructions on yasb to set up.

I used yasb : https://github.com/denBot/yasb

I develop and maintain a twm for Windows and one of the things that I implemented after many requests was a subscription service to allow other applications to listen to and respond to events emitted by the window manager. This allowed people to make stuff like status bars that integrate with and respond to the window manager's state changes.

A push-based event subscription API that allows other applications to subscribe to the latest komorebi events. This is in particular super useful if you want to write your own statusbar. yasb is a great example of a status bar written in Python that subscribes to the latest events from komorebi to always show the most up-to-date information about workspaces and application windows to the user.

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).