Is an image display website better suited for procedural or OO programming?
<p>I have a comics website, <a href="http://hittingtreeswithsticks.com" rel="nofollow">http://hittingtreeswithsticks.com</a>, and I guess I'm unclear as to which style, procedural or OO, that it's written in.</p>

<p>Basically, there are several "templates", homepage.php, viewall.php, viewFullSize.php, which call upon various scripts... namely, the templates all include imageDisplay.php, which has several scripts which determine how to query based on which category, tag, or subsite is selected.</p>

<p>I've read a lot about the benefits of OO programming- when it's used and when it's not... but am still having trouble answering this question.</p>

<p>The way I understand the difference between OOP and procedural from an example standpoint is:</p>

<p>OOP: If you have a website where a user can create an object, such as a forum where a user can submit a post... then you'd want to go with OOP because you'd want to allow users to create several instances of the Article class.</p>

<p>Procedural: I went with what I think is procedural because my comics website simply displays comics out to users. A user can submit a comment using DISQUS, or like/dislike. I don't see where I'd be able to fit the OOP paradigm into a simple image display site.</p>

<p><strong>So, the question is:</strong></p>

<p>To use OOP, do you necessarily need to have several objects that would be instantiated? Or are there other benefits I'm missing?</p>

<p>Thanks</p>
