Microsoft .NET programming can involve lots of design patterns in a single app. Two that I hear much about but never see implemented are MVP and MVVM. The only people I see implementing these patterns are the ones putting together examples of how to use them. Which says to me they have no value.
My question is: Do you see any value in these two patterns and why?
Even listening to the experts, they have a difficult time describing these patterns and what use they are. In the real world, I've never seen an app that is only data binding straight from the DAL (MVP) without some additional logic to filter data into objects and then bind those objects through a more complicated process.
Environments such as Cocoa and Cocoa Touch use MVC. Ruby on Rails has a setup that guides you into a single design pattern. It's easy to talk about these environments and they're patterns because they are explicit. .NET on the other hand is like a mutt where people string together all sorts of patterns into a single app.