On Sun, 14 Oct 2012 01:12:30 +1100 Chris Angelico <ros...@gmail.com> wrote:
> On Sat, Oct 13, 2012 at 3:49 PM, <nbvf...@gmail.com> wrote: > > Basically its a framework that forces the developer(s) to strictly separate > > the model from the view and controller. You can 'hook up' multiple > > controllers to a project. The model layer can be completely mocked out so > > front end designers don't have to bother setting up > > Postgres/rabbitmq/whatever. > > I don't like frameworks that force too much. Actually, I guess that > means I don't like frameworks at all, I like toolsets. Let the > programmer decide what he wants to do. > > That said, though, there are times when a good framework can do 90% of > your work for you. The trouble comes when you want to do something the > author didn't think of - you might well end up either fighting against > the system, or modifying the framework to suit your task (and that > works only if you created it yourself). Thin frameworks are usually > immune to this, but on the flip side, they're less likely to be doing > most of your work for you. > > It's really easy to demo something and show how awesome it is. How > easily can it be turned to a task it was never built for? Perhaps we deserve such lame/mediocre web frameworks after all, as Imagination is for those who deserve the freedom to use it properly. > ChrisA > -- > http://mail.python.org/mailman/listinfo/python-list -- Etienne Robillard Green Tea Hackers Club Fine Software Carpentry For The Rest Of Us! http://gthc.org/ e...@gthcfoundation.org -- http://mail.python.org/mailman/listinfo/python-list
