I also did Python first, web second and was fortunate enough to have the time to compare pretty much every single framework out there. The main reasons web2py is my preferred framework:
- it is lean and easy to understand 'all the way down' - this means you are not forced into doing anything the $FRAMEWORK way - it can run anywhere (even embedded and against almost any database engine. I'm running all our apps in dev on my phone) - it is extremely productive to develop with - the documentation and community support is outstanding (and as I said, if needed, just read the source in gluon -it is awesome) In short, we achieve the best mix of freedom (implementation and deployment), productivity and support, which makes most tech sense to me and business sense to our agency. With a Python programming background, I agree that the criticisms against web2py indeed lack merit when actually having a deeper look. In fact, the way web2py works at its core makes a lot of sense to me in a web context.
