Re: what's all the about then?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



tedd schrieb:
At 4:34 PM +0200 8/30/06, Jochem Maas wrote:
tedd wrote:
 At 2:19 PM +0200 8/30/06, Paul Scott wrote:
Read up on MVC (Model View Controller) and the front end controller
 design pattern.
 Interesting that someone finally put a name to something we've been
 doing for decades. We used to just call it input, process, and display,
 which to me seems simpler. In addition, if one used IPD, it's acronym
 would at least be in the right order.
seems whenever I write something that resembles a FrontController I end up
with a process() and a display() method ... small world.
No, it's just that these organizational problems have been around since the days of rock programming -- that's what "Design Patterns" are, namely trying to identify, organize, and reuse code. That's something else we've been doing for decades that has a brand new name.
Design patterns arn't new at all! In fact the big book of Design Patterns is was written twelve years ago!

Well, 12 years ago is new to me and there are new books being published today. And, what I said above about "Design Patterns", is what you said below.

see: http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29

There's a surprisingly number of old techniques that have been given a new coat of paint and sold as the latest model. The key is to recognize them, perhaps I should coin a new name for that, maybe "Concept Evolution", "Process Inheritance", or "Legacy Identification" -- but, to really get it accepted, it has to be complicated enough to impress. :-)
Thats what Design Patterns are about. Describe abstract solutions for object-oriented problems which dozens of programmers had already to solve and present them in a way each programmer understands and give them a name which everyone can understand. Its not to impress people with complicated ideas but to simplify the communication between programmers and give them hints how a problem could be solved.

No, you missed my point -- many books written to simplify, don't. That's the reason some books are better than others for different audiences. Some books appear to have been written to impress peers rather than to teach. If you think different, that's OK, but that doesn't make my statement less true.

tedd

--
-------
http://sperling.com  http://ancientstones.com  http://earthstones.com

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php


[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux