On Wednesday 26 January 2011 10:53:34 cjrh wrote: > On Jan 26, 6:51 am, Alfonso de la Guarda <[email protected]> wrote: > > As an architect I have the power to choose the framework, but I would > > support it in more technical reasons, so that by sharing experiences, > > I will be happy to read their views, especially in management, > > deployment and DAL / ORM > > You should build an application, the same application, with both > Django and web2py. It doesn't have to be a big thing, just try to > cover a few of the basics. This is the only way to really know what > the relative merits are. I did this, and I selected web2py, but in > all honesty, Django and web2py are very close to each other. The > thing that slightly tipped the balance for me was that it seemed > easier to get stuff done in web2py. There were more conveniences.
Having used both, I can say that web2py is indeed awesomely convenient with a great feature set, whereas Django has a hell of a lot of addons and extensions. Both are equally well documented and have nice communities. However, I'm not entirely sure how well web2py scales compared to Django, maybe someone can share some experience on that. I'd be interested in some successful deployment scenarios for bigger sites. -- Mit freundlichen Grüßen, Sascha Peilicke http://saschpe.wordpress.com
signature.asc
Description: This is a digitally signed message part.
