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

Edit page

Title:

Security Code:

Body: (use this wiki markup)

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:

<http://mdp.cti.depaul.edu/examples/static/web2py_vs_others.pdf>
(if you find something is incorrect let us know and we will fix it)

or the wikipedia comparison (less detailed)

<http://en.wikipedia.org/wiki/Comparison_of_web_application_frameworks>

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

<http://mdp.cti.depaul.edu/AlterEgo/default/show/76>

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, web.py, 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](http://mdp.cti.depaul.edu/AlterEgo/default/show/101)

If you know TurboGears you may want to read [this](http://mdp.cti.depaul.edu/AlterEgo/default/show/102)

If you know Rails you may want to read [this](http://mdp.cti.depaul.edu/AlterEgo/default/show/103)

If you know PHP you may want to read [this](http://mdp.cti.depaul.edu/AlterEgo/default/show/106)

This is the web2py FAQ, not a blog.

AlterEgo

old web2py blog

Useful Links

Edit page