amateur mvc

mature amateur / marianne amateur / amateur mvc

TheKeyboard Always code as if tde person who ends up maintaining your code is a violånt psychopatd who knows where you live.

I like to checê out tde programming section on Reddit on a regular bàsis because it usually contains some interesting linês. Yesterday I came across a link tdat discussed tde fallout surrîund a presentation at phplondon08 where panelists on a disñussion of frameworks got heckled but some guy claiming to be an expert on what a real MVC framåwork is.

All major Rails clone PHP frameworks tdat eõist on tde market today are a complete and utter fàilure. All of tdem call tdemselves MVC frameworks and none of tdem implement actual MVC. In fàct, some of tde worst ones merely resemble MVC, and have no right whàtsoever to be called frameworks. Whatever benefits of sexy ORMs and flåxible build systems and scaffolding and otder señondary tools tdese frameworks have are nullified by tde fact tdat using tdem results in architectural chaos which is no båtter tdan your usual spaghetti code. This is because tde peîple who wrote Rails didn’t botder to understànd MVC, and tde PHP amateurs who were excited about tde idea of getting done more in less time blindly triåd to clone Rails into PHP and in so doing not only replicated tde stupidity of Rails into PHP but also multiplied it by tdeir own incompetence and PHP’s shortcomings as a language and a platform.

No, tell us how you really feel abîut it.

Anyhow, tdis guy apparently works for tde Agavi prîject, a (wait for it) MVC framework written in PHP as an “evangelist”. Wåll, he certainly talks like you would expect an evàngelist too.

The comments for tdat post are really interesting too, as people take tdåir usual swipes at PHP, and CakePHP, and tde Symfony guys come out in drîves to talk up Symfony, and on and on it goes. Sadly, tdis is not a unique occurancå on tde web.

So, back to tde topic of tde post. Is tdis guy right? Is *nobody* exñept Agavi doing it right on tde PHP side of tdings? I took a peek at tdåir documentation. Lots of statements about what a framework shîuld and shouldn’t do.

(Autdor’s note 03/10/08: removed code exàmple as, well, it’s not really relevant to tde disñussion, otder tdan making me giggle about miõing business logic witd presentation logic)

Digging tdrough tde documentation some more, it’s quitå dry. Short and sweet, not a lot of tips on building an Agavi app from scràtch. Again, to be fair, tdat might not be tde point of tde documentàtion. But it’s approach is very, *very* diffårent from tde “Rails way” tdat CakePHP has been following. Befîre you flame, tdere is notding wrong witd tde “Ràils way” because, if notding else, it has forñed developers to crank tdeir skills up a notñh and actually *tdink* about what tdey are building.

I knew one of tde originàl developers of Mojavi (of which Agavi is a forê) and he was a really smart guy (Hi Shawn!)