Come on guys, I love you all, contributing your time to help others.
I am sorry but I am trying to be sharp clear with the least number of lines possible.
Me, like most of you, after examining several frameworks think CakePHP is an awesome RAD framework.
Stable, scalable, extensible ....le and easy to profess.
I intentionally spoke about the issue in general manner because none of us, thanks god, read the application requirements.
I also think that recommending a well known open source solutions is the right thing to do most of the time because the project keep on evolving by lots of developers and you benefit as a client from other users needs and security updates that I think no one do in propriety applications if the hole was not discovered by the client.
And the most important thing is the number of users how test the solution.
Neither to say the huge GUI layout available for free, which the client appreciate more, then the clever code we write.
Also Joomla which I know better then Drupal is very extensible.
Anyway, two more things that should be considered while implementing out of the box solution.
1.Delivering a production ready Joomla application is not automatically cheaper then implementing from scratch with cake, the client most of the time think it is.
even if you find all the plugins and extensions you need and really don't need to develop anything, just integrating those components together can cost a lot especially in testing time.
2. Although the Joomla base code is well written, external code from the community vary and some of the code is very poor.
Correcting this code will again cost.
@LunarDraco I agree with you that there is nothing quite like a good debate!
Happy coding
Check out the new CakePHP Questions site http://cakeqs.org and help others with their CakePHP related questions.I am sorry but I am trying to be sharp clear with the least number of lines possible.
Me, like most of you, after examining several frameworks think CakePHP is an awesome RAD framework.
Stable, scalable, extensible ....le and easy to profess.
I intentionally spoke about the issue in general manner because none of us, thanks god, read the application requirements.
I also think that recommending a well known open source solutions is the right thing to do most of the time because the project keep on evolving by lots of developers and you benefit as a client from other users needs and security updates that I think no one do in propriety applications if the hole was not discovered by the client.
And the most important thing is the number of users how test the solution.
Neither to say the huge GUI layout available for free, which the client appreciate more, then the clever code we write.
Also Joomla which I know better then Drupal is very extensible.
Anyway, two more things that should be considered while implementing out of the box solution.
1.Delivering a production ready Joomla application is not automatically cheaper then implementing from scratch with cake, the client most of the time think it is.
even if you find all the plugins and extensions you need and really don't need to develop anything, just integrating those components together can cost a lot especially in testing time.
2. Although the Joomla base code is well written, external code from the community vary and some of the code is very poor.
Correcting this code will again cost.
@LunarDraco I agree with you that there is nothing quite like a good debate!
Happy coding
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to
cake-php+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
No comments:
Post a Comment