Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Posted on
- Cake PHP RAD Framework
- P E Schoen
February 21, 2011, 12:43 am
rate this thread
(http://cakephp.org /) up and running, after hours of confusing errors =
later found were caused by installing it in the wrong place in my xampp=20
Apache localhost. Here is a simple tutorial video that helped a lot:
This is part 1 of a series, and I also found part 2 invaluable. Then I =
proceed to build a blog application using the tutorial provided by Cake =
Although this is not as convenient as the Borland Delphi IDE (and =
its PHP cousin http://www.embarcadero.com/products/radphp ), it does seem =
simplify some aspects of creating a web application using PHP and MySQL =
SQLIte, etc.). And perhaps more important is enforcing certain =
that may help with organization, portability, and maintenance of a =
Does anyone have any experience with this? Thanks.
Re: Cake PHP RAD Framework
Hi Paul, thanks for sharing.
I dived into cakePHP once, and didn't like it at all.
[This is just my opinion.]
The reason I disliked it is NOT because of the MVC-implementation as
done by Cake, but because I dislike MVC approaches in general a lot.
In my humble opinion it gets in the way of experienced programmers, and
hinders newbies to get a real understanding of what is going on.
Also, the 'black box' approach to actual queries is not really helping.
If I want to design complex queries, and keep an acceptable query-speed,
I had to rewrite them myself. (And that can be done in CakePHP.)
Of course, if you design straightforward webpages with little data
complexity, you can quickly develop with Cake.
But seriously, I think every webdeveloper has his/her own sets of little
libs and functions to gets things done quickly. I don't need a
MVC-straight-jacket approach to create clean and simple code.
The 'quick development' advantage of MVC isn't that big in my opinion.
But that is old news. (The old MVC pro/con discussion.)
The Good Thing about an uniform approach with MVC is the fact that, in
theory, is should make things easier for other programmers when they
take over the job.
That is only partly true.
I once took over a project done in CakePHP and was totally confused.
I blamed it on the fact that I only had (modest) MVC experience, and
mainly in Java.
So after studying a few days, I asked the help of a friend, a more
seasoned CakePHP developer, to help me get on speed with the code.
His observations were that the code was a mess, most things were done in
a way that should be done like that in CakePHP, he had to look all over
the place to find the most simple settings.
All kinds of preload/login checks were in place on every page: they
contained long pieces of code, with little to none comments.
So I politely tanked my client for taking over that job. ;-)
Before somebody says: "You can screw up in any language/system", I would
like to say: "And also in MVC."
I would advise all newbies to avoid MVC and learn the language and all
that comes with it the real way.
It is a much more rewarding learning experience and leads to better
Who wants a webdeveloper that never heard of SQL-injection because that
problem was abstracted away by MVC? Who wants a webdeveloper that cannot
design a database him/herself? etc.etc.
That said: I think MVC has its place when used by experienced
programmers in an effort to standardize their coding-approach.
When used as a black-box-"rad"-tool, avoid it.
[This is just my opinion. I don't want to present it as a factoid.]
"That which can be asserted without evidence, can be dismissed without
-- Christopher Hitchens
- » Please test/review my Regex to locate hyperlink in text
- — Next thread in » PHP Scripting Forum