G+_K Denny Posted September 24, 2014 Share Posted September 24, 2014 Episode 35: MVVM +Fr. Robert Ballecer, SJ Just have a question, would anyone know the difference and advantages of using MVC over MVVM or vice versa? Link to comment Share on other sites More sharing options...
G+_Nate Follmer Posted September 24, 2014 Share Posted September 24, 2014 All depends on the type of application you are creating. I'd say about 75% of my web applications/sites use a MVC model (they just make sense when you're working with a database). The Model handles your database... Essentially turning your database into workable data (creates objects from the tables, rows and columns... That's a dangerously generalized statement, but you get the idea). The Controller then handles the interaction between the View and that Model. I've never really done any MVVM designs, so I can't speak there. Link to comment Share on other sites More sharing options...
G+_K Denny Posted September 24, 2014 Author Share Posted September 24, 2014 yeah, I like MVC and have used it a few times and studied the concept, so watching this episode was my first time actually hearing of MVVM, so I was just wondering whats the real difference is Link to comment Share on other sites More sharing options...
G+_Joe Maruschek Posted September 24, 2014 Share Posted September 24, 2014 MVVM was created by Microsoft to aid developing medium- to large-scale WPF apps. By design, it incorporates the Data Binding feature of WPF. If the particular language or framework you are working in has a similar feature to WPF's Data Binding, MVVM might be of some interest to you. Otherwise, I would just use the classic MVC design pattern, since it have been around longer, and it is generic enough to work with a lot of different object-oriented languages and frameworks. Link to comment Share on other sites More sharing options...
Recommended Posts