jordan<p>Am I the only one that hates the <a href="https://mastodon.jordanwages.com/tags/OnPropertyChanged" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OnPropertyChanged</span></a> and <a href="https://mastodon.jordanwages.com/tags/binding" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>binding</span></a> paradigm that permeates <a href="https://mastodon.jordanwages.com/tags/WPF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WPF</span></a> and <a href="https://mastodon.jordanwages.com/tags/Avalonia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Avalonia</span></a> <a href="https://mastodon.jordanwages.com/tags/UI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UI</span></a> <a href="https://mastodon.jordanwages.com/tags/design" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>design</span></a>? 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?</p><p>I can understand for some interactive use cases, but having it be the standard seems bloated to me.</p>