By: Paryank
I agree with you. Programmer should at least know the basics and be able to write his own framework. Well, I haven’t developed my own framework and I use Zend Framework, but I learn the way it works,...
View ArticleBy: Tomáš Fejfar
I went from pure-php-madness to CodeIgniter and from CI to Zend Framework. The first change was a BIG BANG. Complete change of thinking. But (not expected) the other one was even bigger! Great thing...
View ArticleBy: Les
> You can study existing frameworks or read 100 books, but > sometimes the only way to really get it is to screw it up for > yourself. :agree: You have to live and learn; that in it’s self is...
View ArticleBy: till
IMHO, the beauty of some frameworks is the use-at-will architecture. The advantage here is that you can exchange components for a better implementation — or let’s be honest, one that’s more appropriate...
View ArticleBy: Andy Walpole
If by having your own framework you mean that PHP developers should have their own library of tried and tested code, then yeah, I’m 101% with you on this.
View ArticleBy: Bertrand Mansion
I have written my own framework. It is better than anything I have seen because it fits my needs and my colleagues’. I don’t think using an existing framework is a good idea unless you have no other...
View ArticleBy: sole
Every developer who knows ends up writing his/her own framework so that it has *exactly* what he/she needs, and not the myriad of options and modules that ‘established’ frameworks have so that they can...
View ArticleBy: Tomáš Fejfar
sole: Problem is that you never know what you need until you really need it ;) And more heads = more knowledge = less hidden flaws. You never needed to update some data in view and echo it somewhere in...
View ArticleBy: Les
> … but nobody should use it for any serious work. Why not? I can think of one reason – security, however any developer with some experience who could develop their own framework would already know...
View ArticleBy: Tomáš Fejfar
Yes, security is main concern. But what about a lack of documentation, lack of coding standards, etc? :) I’ve never seen a framework, not developed by community, that had good coding standards,...
View ArticleBy: sole
Tomas, if your framework is properly designed, you don’t need to rebuild everything each time you want to add a new feature. I have used somebody else’s frameworks several times and most of the times...
View ArticleBy: Tomáš Fejfar
sole: That’s EXACTLY what I’m talking about! Problme is that everyone thinks about everyone’s elses framework that it’s lame! :) That’s why everyone develops his own. And that’s using a prefabricated...
View ArticleBy: Jayant Patil
Creating your own framework is good thing. I think every developer should make it. But it should have some concept. Why you require it when it is already developed by someone having more features. If...
View ArticleBy: Svetoslav
I think every decision should be based on your task/goal/project. If you want to build a simple & small site then it’s not worth the time of building something sophisticated. Matthew has an...
View ArticleBy: Les
> no docs – you know how it works, why docs? That just wouldn’t happen in a professional evironment, simple as that – if it did, the project manager(s) should be booted the -beep- out of there. I...
View ArticleBy: Paryank
I agree with you. Programmer should at least know the basics and be able to write his own framework. Well, I haven’t developed my own framework and I use Zend Framework, but I learn the way it works,...
View ArticleBy: Tomáš Fejfar
I went from pure-php-madness to CodeIgniter and from CI to Zend Framework. The first change was a BIG BANG. Complete change of thinking. But (not expected) the other one was even bigger! Great thing...
View ArticleBy: Les
> You can study existing frameworks or read 100 books, but > sometimes the only way to really get it is to screw it up for > yourself. :agree: You have to live and learn; that in it’s self is...
View ArticleBy: till
IMHO, the beauty of some frameworks is the use-at-will architecture. The advantage here is that you can exchange components for a better implementation — or let’s be honest, one that’s more appropriate...
View ArticleBy: Andy Walpole
If by having your own framework you mean that PHP developers should have their own library of tried and tested code, then yeah, I’m 101% with you on this.
View Article
