I like web2py and prefer it over RoR but two things I am missing: 1. migrations (RoR migrations are really more powerful, you write the script that not only changes database scheme but also can update data, you have full control etc.) 2. models (web2py model layer is purely database layer which you use by ORM, in RoR models are classes that run on top of ORM and let you program custom methods; e.g. for class 'Users' you can develop methods 'is_logged', 'is_admin', 'dont_destroy_admin' etc etc.)
Many-to-many relations that are supported by many frameworks are actually a drawback and Rails have already changed original concept to 'belongs ... through' which is actually a manual table definition for many-to-many relations; so in web2py you just define a table with all necessary fields for your particular situation. And the biggest advantage of web2py is Python language. It's by far more mature than Ruby and have so many libraries available that you hardly have to develop any system level task, you just script the behavior you need in terms of domain area of your application. I mean, if you want to use statistics you use scipy, you need pdf - reportlab, networking - no problem, AI - no problem. Web2py makes it easy to install libraries and distribute/deploy with your apps. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
