Many thanks indeed David - in that case I'd better start learning pdq!
Feb 13, 2012
MVP (Model-View-Presenter) is a specific design pattern that may take advantage of polymorphism. It's not the same thing though.
Feb 12, 2012
Just my thoughts on this....
I understand what you are thinking, atleast I guess. Yes nowadays most of the technology seems to be buzzword around something very basic. But sometimes this buzzword is required for having a common understanding across teams and different stakeholders. If you consider any aspect of OOP with respect to reuse, then most of them may be achieved using some kind of polymorphic behaviour.
The thing to understand and remember is that MVP is an architectural pattern (another buzzword here), which definitely has its own role to play, much more than the simple term of polymorphism. Its an amalgamation of various other buzzwords, which when bundled together may help you create better applications which is resilent (another buzzword here) to future changes.
Yes you can definitely create applications without using MVC, MVP, but then if its an enterprise applications where various teams are working together, it will be very difficult to communicate design and ideas across consistently though not impossible (but how many people would like to do this) without using a common vocabulary.
A new member joining the team may find a hell lot difficult to browse through the code if there is not a common vocabulary.
So, definitely some times, some buzzwords are necessary, if applied in right context.
Rajesh Pillai, Feb 16, 2012
Apr 19, 2011