Some of the information here may be outdated, please check the book instead

web2py is better because it is faster, it is easier to use, and is more stable than other frameworks. It is also always backward compatible.

You should read the detailed comparison of features here: (if you find something is incorrect let us know and we will fix it)

or the wikipedia comparison (less detailed)

Finally you may want to read benchmark results for the web2p ORM vs other ORMs popular with other frameworks

If you feel the need to say something negative about this framework without having tried web2py and without going to substantiate it with hard facts, please take your rant somewhere else. web2py respects other frameworks and other developers. We have learned a lot from Django, PHP, Pylons, Turbogears,, Rails, etc and we do acknowledge that. So, please, respect us.

more explicit but incomplete comparisons:

If you know Django you may want to read this

If you know TurboGears you may want to read this

If you know Rails you may want to read this

If you know PHP you may want to read this

This is the web2py FAQ, not a blog.

© 2008-2010 by Massimo Di Pierro - All rights reserved - Powered by web2py - design derived from a theme by the earlybird
The content of this book is released under the Artistic License 2.0 - Modified content cannot be reproduced.