[EMAIL PROTECTED] (Robert Cummings) wrote in news:[EMAIL PROTECTED]:
> Regardless of the framework or library or whatever you choose, you > WILL have to adapt to it to some degree. Whether that be style-wise or > just learning the the API. The more power, and flexibility you want, > the more you will probably have to learn. These things usually come at > the price of learning a very specific way to do something, but once > learned, becomes extremely quick to implement and adapt. I'm not averse to learning a methodology-- I learned Fusebox in just this situation when I was using Cold Fusion. However, when I made that choice there wasn't much to choose from and the basic model made sense. With PHP there is a LARGE number of frameworks to choose from, some of which seem amazingly complex, some of which appear to be seeking theoretical ends rather than practical solutions. Templating solutions have never been my thing, so I have a bit of a built- in resistance to that concept, and I'm not programming for IBM, so I don't necessarily need a framework that is suitable to the largest enterprise. I'm not even particularly worried about interoperability with parts of program A and program B, which seems to add a lot of overhead to, for instance, the fusebox model, where they are trying hard to make each fuse portable. c -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
