Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • don't you think these model-view architectures are best understood by the people implementing them. I believe it's matter of choice for the developer. One choose MVC or MVVM depending whether he wants a total abstraction about the view with a little over-head(in case of MVVM). Commented Aug 31, 2011 at 8:05
  • @Pankaj Upadhyay: Which one you should use depends on your requirements and choice of technology and also the idiosyncracies of your platform. Commented Aug 31, 2011 at 8:15
  • I believe that MVC architecture is good enough for anything, but that might be because i haven't faced a problem that particularly required MVVM. IMO, you certainly need to have some control over the view because making it absolutely loose will enhance more errors in future upgrades Commented Aug 31, 2011 at 8:22
  • 1
    @Pankaj Upadhyay: If you want to use the same logic for various UI technologies then MVP is superior. I don't think that you necessarily need some control over the view. It can be totally independent and you can test the ViewModels just as well - if not better. The better separation also benefits designers as the work on the project can be partitioned better. Commented Aug 31, 2011 at 8:33