I really tried to get into WPF a while back, I learned PRISM and MVVM and tried to go all in. What I found is that most of the time when I build a tool or a win

I really tried to get into WPF a while back, I learned PRISM and MVVM and tried to go all in. What I found is that most of the time when I build a tool or a windows app its usually a tool for automation or data manipulation. What using MVVM did was make the UI take 3x longer to build, usually (and this is my admitting Im not a designer) would not be as easy to use or read as standard winforms, and honestly was complexity for complexities sake. I still use plain old winforms and c# and can make really usable, skinnable UIs with my DevExpress controls. Maybe if I were building an app that had requirements for chat, multimedia or some other use case that I dont need the Xaml ui paradigm works. I dont like Flat UI, and I personally think that the UI in Teams and One Note are a step backwards in usability. I had a PC that for a specific reason needed to have hardware acceleration disabled for the video. What that meant was that OneNote was broken. The UI would not display correctly- the note pages were blank unless you grabbed the UI with your mouse and moved them slightly. Winforms just works on every windows box...