Talking with some python veterans (mainly SQLalchemists ;-), their critique of web2py was summed in two words, "exec magic." In practical terms, what does this mean... in terms of performance hits (at N requests/sec), inefficient CPU / resource consumption, etc. ?
And ditto for MVC caching... In general, how does one test a site under heavy usage conditions? __ Thanks to Robin B for her insightful comments She mentioned: "making web2py more productive requires changes that break backwards compatibility." The time for a major web2py revision could coincide with python 3.0 -- Guido in http://bit.ly/py3k mentions a lot things which will break anyways without code modifications. Also see his remarks re exec. Re critique: "Use WSGI middleware to customize applications (caching, routes, exception handling)" Why did you choose web2py over pylons? __ Thanks to Massimo fixing the compiled pyc problem for GAE At http://bit.ly/web2py-cloud he has expressed his willingness to support SimpleDB which will great for computing on the Amazon cloud. __ Thanks to all other members for your detailed responses. PERMALINK for this thread at this web2py group: http://bit.ly/web2py-critique On Nov 28, 7:51 am, Robin B <[EMAIL PROTECTED]> wrote: > > 1) did you experience any scalability problems with web2py? > > More of an efficiency problem: web2py's exec magic means models, views > and controllers are read, parsed and compiled for every request on > GAE. > > > 2) How large did you scale it? > > Not large > > > 3) What are the features that you believe are missing in web2py and > > you would like to see in future versions? > > Models, Views and Controllers as classes, so you can mixin new > behavior without copy-paste > Environment modes (development, testing, production) > Better plugin semantics (versioning, dependencies) > Use WSGI middleware to customize applications (caching, routes, > exception handling) > Fix template nesting bug > Named routes, RESTful routes > MVC caching > > > 4) How does it compare do other web frameworks that you have used?" > > Web2py is the most productive and thanks to GAE most scalable > framework I have seen, but making web2py more productive requires > changes that break backwards compatibility, so you need version 2.0 or > a new framework... > > Robin > > On Nov 28, 8:46 am, mdipierro <[EMAIL PROTECTED]> wrote: > > > Hi 43gm, > > > if I understand your email you are seeking critiques form other users. > > You are particularly interested in potential scalability problems. did > > I understand? > > > If I do I would rephrase your request into the following explicit > > questions to the users: > > > 1) did you experience any scalability problems with web2py? > > 2) How large did you scale it? > > 3) What are the features that you believe are missing in web2py and > > you would like to see in future versions? > > 4) How does it compare do other web frameworks that you have used?" > > > You also express one critique about the use of the word "enterprise" > > in the name. That is explained > > herehttp://mdp.cti.depaul.edu/AlterEgo/default/show/166 > > > You can also find a comparison of features between web2py and other > > frameworks > > here:http://mdp.cti.depaul.edu/examples/static/web2py_vs_others.pdf > > > Massimo > > > On Nov 28, 1:05 am, 43gm <[EMAIL PROTECTED]> wrote: > > > > 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 GAEhttp://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 -~----------~----~----~----~------~----~------~--~---
