Tuesday, December 14, 2010

Code Base Fragmentation -- Again

Check this out: "Stupid Template Languages".

Love this: "The biggest annoyance I have with smart template languages (Mako, Genshi, Jinja2, PHP, Perl, ColdFusion, etc) is that you have the capability to mix core business logic with your end views, hence violating the rules of Model-View-Controller architecture."

Yes, too much power in the template leads to code base fragmentation: critical information is not in the applications, but is pushed into the presentation. This also happens with stored procedures and triggers.

I love the questions on Stack Overflow (like this one) asking how to do something super-sophisticated in the Django Template language. And the answer is often "Don't. That's what view functions are for."

1 comment:

  1. Actually it can't violate the rules of Model-View-Controller, because Django doesn't implement MVC in the first place. It's some variation of PMVC or MVP at best.


    And since you are already stretching the definition, I fail to see how adding real presentation logic is bad. (And said example is not nearly as bad, btw, as some PHP code *cough* osCommerce *cough*.)