Taking the Sting Out of PHP 5 Programming

bfioca writes "Where are the all-in-one PHP frameworks that make building well-factored and maintainable applications as easy as building simple sites? O'Reilly ONLamp's recent article Simplify PHP Development with WASP shows how to make a simple database-backed site with WASP in just a few lines of code. Other PHP 5 frameworks such as symfony and PRADO have been getting a lot of recent attention as well."

Comments

What about PHP using HOOD?

[dotslashdot]

For the rest of us hip hop inclined programmers, there is PHP using HOOD (Hizous Object Oriented Development) in case you get tired of the WASP crowd.

SNOOP development?

[dotslashdot]

And don't forget SNOOP (SNoop Object Oriented PHP) for the rest of the hip house crowd who doesn't like the Country WASP crowd.

Re:I need PHP

[Charbax]

I think it should be possible to have a GUI application, that let's the user design a database. Then this GUI let's the user assign some functions between each table of the database. And at last define the .php pages and design them with Wysiwig. Lastly the .php files are uploaded to the server and it should work! That's what I am looking for. But for now I will try cake, prado and symfony and see what I can do with them.

Re:Modern web programmers have moved elsewhere

[GigsVT]

Lately, however, a lot of programmers have moved onto Ruby on Rail

No, they haven't

You are buying into the hype. Apparently a miniscule but vocal minority of people have even heard of Ruby on Rails. Most of them seem to read this site.

Where has gone the REALLY good ideas, namely, KISS

[Skal Tura]

all i can say: WTF is this?
Has all wise people suddenly disappeared?
Where has the philosophy of KISS disappeared? namely: Keep It Simple, Stupid!

WASP seems far from simple, let's take this example:
Request::getParameter('Add') != null
wtf? Why can't one do $_POST['Add'] != null?
What format even is Something::Something ??

TaskWrapper?

What's so bad with plain Modular Design + Smarty?

I can do easily with it after building the init scripts (transfearable from project to project) something like this with 8 lines or so.
namely
if ($_POST['Add'] != null && $_POST['Job]' != null) {
      $Job = Validate($_POST['Job'], 'string'); //my own function
      DoQuery("INSERT INTO 'todo' VALUES('', 'Job', '" . timestamp() . "')"); // again here is my own functions
}
??
Note that is untested code etc. and probably wrong :)
I could bet that WASP doesn't have such an good documentation too, making it harder to development.
Why do we need PEAR objects for everynew project? etc.

You can do hell of a fast code with standard PHP too, tested dozens of times that ain't even hard if you just remember KISS.

Now, i've done a browser game (http://www.paradox-online.net/ ) with PHP, also i'm working on a framework (http://framework.artichost.net/ ) and game will be using it in future as the basis. So i know what i'm talking about.

Now, could someone make me see the PRO side of using WASP for example?
In my eyes, all WASP does is adds complexity, which NEVER is good. You need to KISS it, make it easy to maintain, easy to debug, easy to read etc.

You have to work on some massive things before you realize that, complexity ain't the way to go. (My browser game, over 14k lines of PHP code initially... cutting it down a lot at this dev period on it, while increasing features... all thanks to KISS philosophy... Oh yeah, you can cut most loops of queries straight at the MySQL query, making your code even shorter and more fault tolerant... ;) so remember KISS)

Re:actually, the "sting" of php5 is...

[acroyear]

Ruby has yet to show itself to me as "something better". it simply "something else". Python was "something better" and has managed to still be too damn much trouble every time I say "i'm going to do this project in python so i can learn the damn language".

and go back and read my post: even if i wanted to switch, i might not be able to because my webhost company may not support the language (though with mine, i could probably talk them into it if i felt like it), and that doesn't solve the REAL problem of PHP (upgrades break backwards compatibility), it merely sidesteps it by changing dependencies.

There is nothing in Ruby so far that has shown me that it won't be doing exactly the same thing of breaking backwards compatibility ever major upgrade the way php has.