7 ms·
https://xkcd.com/927/ https://xkcd.com/927/
by chizhik-pyzhik 4y ago
https://xkcd.com/927/ https://xkcd.com/927/
- neonsunset 4y agoUnfortunately, this XKCD post is used correctly. .NET is known for its homogeneity and massive standard library that seems to be a black hole where eventually all good implementation of popular libraries end up in. With one exception: UI frameworks. For whatever reason, UI frameworks have bloody and complicated history starting with early versions of .NET Framework and ending with the latest upcoming .NET 7. Let's hope, fingers crossed, this time is different :D
- yakkityyak 4y agoI would actually go as far as to say that even in a Microsoft-only vacuum, they have cornered themselves into this exact xkcd post. If you are working in C#, Microsoft offers at least 5 different UI frameworks to choose from. Off the top of my head there is WinForms, WPF, UWP, WinUI, and now MAUI. All of them step over each others toes to some degree. As far as I know, it's still impossible to write apps that can fully incorporate the late Windows 10/11 acrylic design language. WinUI 2 & UWP is basically dead, and it still seems like WinUI 3 dropped support for it.* So if I'm a writing a new app and actually want to adopt the new design language, it still seems like you are stuck with no options. 1. https://github.com/microsoft/microsoft-ui-xaml/issues/2236 https://github.com/microsoft/microsoft-ui-xaml/issues/2236 EDIT: after some further sleuthing it sort of looks like window acrylic might show up in WinUI 1.1 coming sometime this year, but it's not so clear.