yintercept's Journal: PHP ... An Object of Frustration

I am sitting here upgrading a program (Community Color) to PHP 5. I originally wrote the program procedurally since there were people on the project who were new to OO programming.

So, I sat down and rewrote the program with a full object model, and now my brain is screaming because, writing everything out in a full object model, seems to be adding all sorts of extra overhead. If this was PL/SQL, Java or C++, I would be extremely happy with the new program. However, the full object model just doesn't feel right for a scripting environment like PHP.

The idea for this site was just to be a mindlessly simple directory and calendar. The same page gets pulled up a large number of times.

Each page is a very distinct path through the object model.

Here is what is sitting in my brain: A path through an object model is a procedural program. If each call goes through the same path, then why not just accept that, and take advantage of the efficiencies of straight procedural programming?

The other part of my brain screams: people think less of programmers who write procedural code. No-one, other than myself, will ever buy the idea that the procedural programs I had written were in fact simply a pathway through the object model in my mind.