Re: Zend Framework...where to start? -- don't.
| From: | Phpster | Date: | Thu, 15 Jan 2009 15:22:56 +0000 |
| Subject: | Re: Zend Framework...where to start? -- don't. | ||
| References: | 1 2 3 4 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-286433@lists.php.net to get a copy of this message | ||
On Jan 15, 2009, at 10:19 AM, "Boyd, Todd M." <tmboyd1@ccis.edu> wrote:
Awesome :-) Bastien-----Original Message----- From: Paul M Foster [mailto:paulf@quillandmouse.com] Sent: Wednesday, January 14, 2009 8:18 PM To: php-general@lists.php.net Subject: Re: [PHP] Zend Framework...where to start? -- don't.---8<---I agree and disagree. I agree there's waaay too much herd mentality in the programming field. (Fortunately, Linus Torvalds didn't listen to the academics who insisted that microkernels where THE WAY, or we wouldn't have Linux today.) OO is nifty for some things, but it's certainly not the "fountain of reusability" it was originally promoted to be. And I also agree about tables versus CSS. I can render a page very precisely with tables that would take me hours to get right with CSS. And I really don't give a crap about what "experts" say about anything. I find "experts" to be wrong much of the time. OTOH, I just finished writing about 80K lines of PHP/HTML, all byhand,no OO, no classes, no nothing. Each page in one file, except for a few helper functions in a couple of common files. I wouldn't want to go through that again. I've opted for a framework on rewriting this code, just to cut down on the number of lines of code I have to manually write. But I built my own framework, which doesn't call in 20 filesforeach page load. Very compact. Probably not suitable for every kind of project, but it works for this. Incidentally, I would differ from the reviewer in the link above only in this respect: He maintains that every line of code adds time. While this is true, I believe it's the number of files which have to be opened which drags down framework numbers the most. When I wrote C code, the CPU would blaze through the actual code, but file opens and reads consumed far more time than in-memory code execution.http://www.giveupandusetables.com 'nuff said. // Todd -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php