Ancestors

Toot

Written by jordan on 2025-01-01 at 00:26

Am I the only one that hates the #OnPropertyChanged and #binding paradigm that permeates #WPF and #Avalonia #UI #design? It feels like its the "proper" way to set up the UI, but it's so much cruft when, for example, you've got to actually do something with the values in the view at the end of it's life anyway. Why not just populate values at the initialization and read them when you need them?

I can understand for some interactive use cases, but having it be the standard seems bloated to me.

=> More informations about this toot | More toots from wagesj45@mastodon.jordanwages.com

Descendants

Written by Max on 2025-01-01 at 01:05

@wagesj45 I recommend ReactiveUI and/or “one-way” “Redux flows” based on immutable records, for what that is worth.

=> More informations about this toot | More toots from max@smeap.com