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 | View the thread | More toots from wagesj45@mastodon.jordanwages.com
=> View onpropertychanged tag | View binding tag | View wpf tag | View avalonia tag | View ui tag | View design tag This content has been proxied by September (3851b).Proxy Information
text/gemini