by Howard Miller.
I slightly regretted saying that after I typed it - not because I don't think it's true, more because I don't think I explained myself very well.
I meant MVC as a design pattern to be religiously followed rather than a sensible separation of the system into discrete components. Thinking you *have* to use MVC for any web application leads you down a certain path that may not be the best solution. What Moodle has is a bit of a hybrid, and there's nothing wrong with that - however, one never did have to write horrible code in Moodle. (I'm not suggesting that I never did!)