Hacker News Reader

Comment by Khelavaster | Hacker News Reader

Responsive UI-driven apps these days use MVC backend => frontend MVC app context loader => frontend MVVM application layer.

https://learn.microsoft.com/en-us/dotnet/architecture/maui/m...

View on HN

MVVM uses two-way data binding. By now it is widely acknowledged that one-way data binding is better.

I wish I was smart enough to understand what this really means, I often feel very much like a code monkey when these discussions come up.

In the old days there was just MVC. Then Microsoft announced successor to Windows Forms... a new technology called WPF. WPF uses MVVM which automated more of the work that a developer has to do: it automatically updates the UI when data objects change, and it automatically updates data objects when the user inputs something through the UI. Sounds cool, right? The problem is that in large projects it becomes hard to understand how data is flowing. Because of excessive automation things are happening behind the scenes. Developers began to understand that this is not as cool as it initially looked. React re-introduced one-way data binding, which updates the screen when data objects change, but not the other direction. People found that they are significantly more productive with this technology even though it does less on behalf of the developer. Now it is widely acknowledged that one-way data binding is better.

... WPF has built-in one-way databinding. You choose whether every control is one-way or two-way...

Reply on news.ycombinator.com