Posted: Fri Mar 02, 2007 7:03 pm
mmm spam
A community of PHP developers offering assistance, advice, discussion, and friendship.
http://forums.devnetwork.net/
Wow ... that' pretty impressive. So for all customers and all solutions? And given that there is no one specific MVC implementation because it is such a general pattern? Either you are ignorant regarding MVC or you are a visionary way out ahead of today's best and brightest!david2007 wrote:MVC is unproductive and unprofitable for the customer who's paying for it.
I haven't seen anyone here say that... I'm not advocating that MVC is the be all end all either. It is a way that has been tested time and again that has shown that it works, and fairly well.david2007 wrote:There are other people in this forum and in other who say just about the same thing:
MVC is unproductive and unprofitable for the customer who's paying for it.
The added work on the front end used in creating a flexible framework (MVC or not) to base sites on mostly happens one time (often outside of a client's time) if you're a good developer. Some classes need alterations, but the majority need none for each client. The same can be said for the procedural code that your trying to suggest is better. However, some time and fingers in code later which system is easier to fix, alter or diagnose? Neither, both, .. it's not possible to say entirely. But I can tell you that it's harder to screw things up in an OOP environment than it is in a procedural one. Why do I think I can safely say that? Because I've done both for many many years. The code your friends have written is attempting to be object-oriented procedurally. I'm failing to see how that's revolutionary as you seem to think it is. Maybe I'm reading your words, spoken and unspoken, wrong.david2007 wrote:The only difference is that I'm the only one who says it loud and clear.
Do you know how to count?
Then just make the calculations on how much time you take developing a system with and without MVC.
Just plain arithmetics, dude!
Ok. I'll make some number up based on a 'best guess'. I've been writing websites and web apps for over 10 years so I imagine the numbers aren't too far off.david2007 wrote:Then just make the calculations on how much time you take developing a system with and without MVC.
Just plain arithmetics, dude!
I guess this depends if you have clients that want things shipped out as fast as possible, and not concerned with the lifecycle of code. Sure, I could spit out a a 100,000 lines of an application in a month or two that was written in procedural code but I'll be damned if they ask me to debug errors that have crept up 6 months later.arborint wrote:Wow ... that' pretty impressive. So for all customers and all solutions? And given that there is no one specific MVC implementation because it is such a general pattern? Either you are ignorant regarding MVC or you are a visionary way out ahead of today's best and brightest!david2007 wrote:MVC is unproductive and unprofitable for the customer who's paying for it.
Code: Select all
class IndexController extends Northern_Controller
{
public function IndexAction()
{
$this->view->paintOutput($this->model->getListing());
$this->getResponse()->appendBody($this->view->render());
}
}Code: Select all
class IndexView extends Northern_View
{
public function paintOutput()
{
$this->set('test', 'this is a test');
}
}Code: Select all
class IndexModel extends Northern_View
{
public function getListing($listing)
{
return $this->fetchAlll('SELECT * FROM `listing`');
}
}Code: Select all
<?php print_r($this->listing); ?>