Answers
MVC - 4
ololo
good balance between what you can do , what you should do, what you can't do.
MVC seems to make sense in many different programming situations. The other two, MVP and MVVM, are more specialized and makes sense in those narrower environments.
Default Business logic has'nt to implemented at all but is merely satisfies ba the scaffold.
MVP - 2
It can be used for both winforms webforms and flash/flex/silverlgiht
Because...IT IS!
MVVM - 6
It binds the data as far back as possible resulting in minimised need for code behind in the view.
it is completed loosly coupled architecture. each does't know about the other
No need to write event driven application and having better for unit testing.
Because of no coupling between the layer and we can mould the code as per our requirements.
my fav
Not only the seperation between view, data mode, and business logic, but also the dynamic data binding in realtime.
