Re: Zend (or other) Framework...where to start?

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

 



On Wed, 2009-01-14 at 17:59 -0500, Paul M Foster wrote:
On Wed, Jan 14, 2009 at 04:30:59PM -0500, John Corry wrote:

> Well, bummer.
> 
> I *seriously* need to divine a way to increase my efficiency both
> immediately and for the long term as I maintain tomorrow the
> applications I build today.
> 
> For the new-to-frameworks, is there a better/easier framework to use
> that will streamline the development process from the beginning?
> 
> I've looked at Codeigniter and LOVE the user guide/documentation...the
> underlying philosophy of that product looks very attractive too.
> 
> Any others?

If you're going to go with a prebuilt framework, I'd recommend
CodeIgniter for your first time out. If the docs look good to you (and
they are pretty good), you'll probably do fine with it. It's about the
lightest weight platform out there. It doesn't get in your way too much,
but gives you the benefits of using a framework.

My beef with frameworks like this is that they have too much cruft. I
checked one time and codeigniter (again, one of the *lightest*
frameworks) open about 15 files before a byte gets written to the
screen. There is a lot of stuff in there you don't need (benchmarking
code, etc.). I'd hack that stuff out if I were using it for real.

One of the things you'll have to get used to is the MVC way of doing
things. When you first start writing PHP, you probably don't do things
this way, but when you start using frameworks, you've got to starting
thinking in terms of what the view will do, versus what the controller,
versus what the model will do. It's just a change of viewpoint you have
to get used to.

In any case, I've used CodeIgniter and liked it. I just didn't like all
the cruft in it. And their license is not a straight GPL-like license--
it requires attribution even on derivative projects and requires clear
notice of any changes you make to their code. But for a framework, it's
pretty good.

Paul

-- 
Paul M. Foster

OMG, and don't get me started on ORM. What a bloat that is. The amount of query overhead is rediculous. All these stupid objects for even the simplest of 'glue tables'. Straight SQL, optimized for your query and the data you need is significantly faster. But if you try to use that in a framework, you have other drama to deal with. Here is the base.class.php I wrote that gives the best of all worlds IMHO...

Attachment: base.class.php
Description: application/php

-- 
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