Posted by Tony Marston on 12/17/52 11:53

"bryan" <tekhneek@gmail.com> wrote in message
news:1153515390.364720.117780@m73g2000cwd.googlegroups.com...
> PHP started out as templating engine. Why would you want to use a
> framewore? that's like creating an abstraction layer for a PHP
> abstraction layer... too redundant.
>

A templating engine is not the same as a framework. Every application that
consists of a large number of components needs a framework so that
components can be created as individual units, then plugged into the
framework so these individual units can work together as a whole.

At the very least a framework contains a basic menu system which informs the
user what options are available and allows him to choose one. Nobody (with
any sense that is) will include this common menu code into every
application module. The next step is to add security into the framework so
that individual users can only choose options for which they have
permission. Again this code goes once into the framework and not into every
individual module.

The idea that everyone should be forced to use the same framework is utter
nonsense. There is, and never will be, a single framework in any language
that will be all things to all men. Just as there are different languages
for different purposes there are different frameworks for different
purposes.

--
Tony Marston
http://www.tonymarston.net
http://www.radicore.org

[Back to original message]