well im not trying to convince everyone to start doing oop, just because i dont have time. maybe if i get rich and have time ill go on a dedicated mission or something. anyway i think its obvious that objects are powerful. look at the big php projects out there; wikipedia, facebook, many of the new frameworks that are coming out. i dont see how you expect to build a big system on procedural code, then maintain and extend it w/o pulling your hair out. but then again i never really studied procedural design. i started out w/ c++ back in high school and been going from there ever since. dont get me wrong ive written assembly for mips and worked with a wide variety of languages, but quite frankly i treat php development much like java development, as a high level language focused on the use of objects and interfaces. -nathan On 7/31/07, tedd <tedd@xxxxxxxxxxxx> wrote: > > At 1:25 AM -0500 7/31/07, Richard Lynch wrote: > >On Sun, July 29, 2007 12:45 pm, Nathan Nobbe wrote: > >> one of the hardest parts about using design patterns in reality is you > >> have > >> to be able to recognize a certain > >> problem and then you can begin to understand how to apply a particular > >> pattern or set of patterns to your > >> solution. > > > >Or, in my experience with pattern zealots, mis-recognize a problem as > >a pattern it isn't, mis-apply the "solution" and then spend years > >dealing with a square peg in a round hole... > > > >:-) :-) :-) > > > >If you're not experienced in the first place, design patterns are just > >a big fat jumble of over-engineered toys that will make a pig's > >breakfast of everything. > > > :-) > > Unfortunately, that's the way I see it as well. > > Cheers, > > tedd > -- > ------- > http://sperling.com http://ancientstones.com http://earthstones.com >
