I have done my research, and have a good impression of web2py. When I read articles on the net, I am amazed at the earnest effort of the web2py creator to add his comments especially when are there are reviews and opinions comparing various frameworks.
Here I would kindly like to request a honest critique of web2py: the limitations, the gotchas, the downside. No software is perfect, and it would be wonderful to know the pros and cons before making a major investment of time and development using a particular tool. I have tried to find info regarding how web2py scales in real situations (not in theory). The reply might be that it scales as good as Google, pointing to the reddit clone at GAE http://web2py.appspot.com -- however, I wondered out loud when I got a ticket for some "unrecoverable error." What are the largest sites that *truly* depend on web2py? [This would address the "enterprise" part to the web2py slogan.] The type of critique sought is not a list of bugs -- one can see those on code.google and launchpad. What is structurally annoying, what gets annoying as a project grows in complexity, is the ORM really efficient at large scale, etc. -- the big annoyances. Viewed in another manner: in what areas should web2py be improved? Thanks very much for your candor. Look forward to your replies... --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
