There are web frameworks and there are web frameworks. I had been using several in PHP:
Symfony (http://www.symfony-project.com)
CodeIgniter ( http://www.codeigniter.com)
CakePHP (http://www.cakephp.org)
And I have been exposed to these in python:
Turbogears (http://www.turbogears.com)
Django (http://www.djangoproject.com)
Pylons (http://www.pylonshq.com)
Currently, though, I involved myself in developing in Turbogears. As easy as it may seem, the problem with
This framework is the ORM is too simple. I don’t know I think it came to me when I think about using symfony project
that made refactoring to the model possible. Tried google-ing “Model Refactoring in Turbogears” but search almost
always comes irrelevant to what I was looking for.
Sincerely, there is no point in using ORMs if the logic of trimming extra data from your model still resides in the
controller. What happens, is, SQLAlchemy mainly becomes a database abstraction rather than an ORM. ( I see, hence mapper????)
I wish other developers would see it my way.
I am not against Turbogears. I like it. I love the way it handles things. I recently learned how to break down controller parts. The thing is
I am not used to using ORMs as database abstraction mechanisms. Might as well go with ADODB ;) ( hmmm at least I don’t have to code
SQL by hand) But that’s just IT! Naked Objects come to view. Every body is going down the way of minimalism. But just how far minimal
should one get? It doesn’t make sense anymore sometimes. People can really be difficult when it comes to decisions like this.
As for now, I will leave all my database queries in the controller, pass them to the view instead of doing the queries in the model, with the controller
being agnostic to what the model contains (WHICH SHOULD HAVE BEEN THE BETTER WAY).
And as far as I am concerned, both languages ARE FAST. It’s just up to the programmer just HOW FAST the software would be.
Good Morning.
Keep the tradition of knowledge sharing alive.
