4 ms·

The common advice nowadays is to not use WinUI directly in .NET land. Instead, it is usually recommended to use AvaloniaUI or MAUI (which, as I've heard, has i

The common advice nowadays is to not use WinUI directly in .NET land. Instead, it is usually recommended to use AvaloniaUI or MAUI (which, as I've heard, has improved). There is a variety of SwiftUI-style declarative GUI packages and built-in APIs to absolve you from ever touching XAML if that's your preference.

cosmic_cheese 2y ago
Really, I don’t need anything trendy like declarative UI, though that can be nice for simpler use cases. Just plain old boring pure-code imperative is perfectly fine, maybe even preferred because it’s been proven to be able to handle complication and nuance more easily than declarative frameworks tend to and is more conducive to VCS than machine-generated XML is.
- neonsunset 2y ago
  Honestly, at this point, I'm so done with "blame the tool for failing to look for solutions or fighting with the way it was designed to be used". Because everything is literally there and is a matter of reading documentation and picking a package/framework which suits your needs. It's not perfect but desktop GUIs are more or less a solved problem in .NET. I will stop trying to help because it's clearly not working.
  - cosmic_cheese 2y ago
    Sorry, didn’t mean to come off as unappreciative. Will definitely keep your advice in mind, I just get a little exasperated with trend-chasing typically getting prioritized over shoring up inadequacies in the UI framework space (even outside of the Microsoft sphere).
    - neonsunset 2y ago
      To be fair your comment is fairly benign and I shouldn't have overreacted, sorry. Seen one too many of replies sharing this sentiment lately. "Poor performance, runtime errors, lack of support for X or Y (when there is one), etc." - the platform makes it difficult to run into many of these problems. And yet whenever something goes wrong, I find it interesting how teams using other languages seem to blame languages/platforms they use much more rarely.

cosmic_cheese 2y ago

Really, I don’t need anything trendy like declarative UI, though that can be nice for simpler use cases. Just plain old boring pure-code imperative is perfectly fine, maybe even preferred because it’s been proven to be able to handle complication and nuance more easily than declarative frameworks tend to and is more conducive to VCS than machine-generated XML is.

neonsunset 2y ago
Honestly, at this point, I'm so done with "blame the tool for failing to look for solutions or fighting with the way it was designed to be used". Because everything is literally there and is a matter of reading documentation and picking a package/framework which suits your needs. It's not perfect but desktop GUIs are more or less a solved problem in .NET. I will stop trying to help because it's clearly not working.
- cosmic_cheese 2y ago
  Sorry, didn’t mean to come off as unappreciative. Will definitely keep your advice in mind, I just get a little exasperated with trend-chasing typically getting prioritized over shoring up inadequacies in the UI framework space (even outside of the Microsoft sphere).
  - neonsunset 2y ago
    To be fair your comment is fairly benign and I shouldn't have overreacted, sorry. Seen one too many of replies sharing this sentiment lately. "Poor performance, runtime errors, lack of support for X or Y (when there is one), etc." - the platform makes it difficult to run into many of these problems. And yet whenever something goes wrong, I find it interesting how teams using other languages seem to blame languages/platforms they use much more rarely.