As a programmer, I found Web2py more appealing out of the box. I did a fair chunk of the Django tutorial, but they started on a bad note by showing me how to add an admin interface and considering it to be some hot stuff (for crying out loud, that's a pretty high level feature and one that you can code yourself on an incremental basis as needed, they should have started with the building blocs).
I was left with the impression that Django would try to do too much for me. For the most part, I find that Web2py does just the right amount not to get in my way (well, sometimes it does too much, but you can turn it off easily enough via flags and such). Given that I had some prior experience in SQL, the ORM was a minus, not a plus. DAL is closer to my comfort level. I guess that's something to consider (whether you are comfortable with SQL or not). Obviously, there is the whole newish factor with Web2py (less documentation, smaller user base), but I found that the community support was adequate to bridge the occasional gaps in the documentation. On Jan 25, 11:51 pm, Alfonso de la Guarda <alfons...@gmail.com> wrote: > Hi, > > My development team is in a debate about which framework to employ, > half like web2py and other like django. I found it interesting because > we used both in projects and everything has worked out well, however, > for this particular project must choose one of them. > 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 > > Saludos, > > -------------------------------- > Alfonso de la Guarda > Centro Open Source(COS)http://www.cos-la.nethttp://alfonsodg.net > Telef. 991935157 > 1024D/B23B24A4 > 5469 ED92 75A3 BBDB FD6B 58A5 54A1 851D B23B 24A4
