I think that if you get MVC then MVVM is really the same - with 1 extra part (ViewModel). The reason MVVM is more useful, in my opinion, is due to the new DataBinding processes. The ViewModel provides useful abstraction and clarity about what a data binding is and how that binding is represented or transformed. Thatโs all thatโs on my mind.
The missing part of MVC is actually in the MVVM pattern, this is just the hidden part of MVVM, in my opinion. If you look at most MVVM infrastructures, most of them provide some messaging or notification system that really provides the missing MVC control.
Think of the ViewModel as the code for your presentation, the presentation as the designer of your presentation, the model as a model, and the notification / message system as a controller, and we have an absolutely equivalent template.
It was a struggle for what I also understood (I was also from the MVC template, but now I love the MVVM template).
source share