I think the most misunderstood fact with web2py is that web2py implementation is improving every day, because of TOP-DOWN approach choosen by Massimo. What does that mean? If someone finds that something has big impact on perfomace, web2py gets changed to better and the users can upgrade safely, because the external simple API of the framework does not change. So critics are welcome, the more the better.
"exec ccode in ...." is not injection? It is IoC for sure. http://en.wikipedia.org/wiki/Inversion_of_control where is it deprecated? I cannot read it. http://docs.python.org/reference/simple_stmts.html#the-exec-statement remove "exec ... in ..." from python? On what basis? if you want a static language go out of python. I wonder what GVR thinks about that. The only good reasons at the moment to change that are: 1) exec statement bug 2) drastic performance improvement Neither is true AFAIK, but maybe web2py's IoC will change, for testing and debugging purposes, this is free (not as a beer) software indeed, so a new solution would be adopted if one comes with a better one instead of talking about plain aesthetics, which is a good thing although it is not alway viable in this world. But if that would happen fear not, we won't notice, we will not have to change our code. mic/mcm 2011/1/7 Philip Kilner <phil.kil...@gmail.com>: > Hi Philip, > > On 07/01/11 18:17, Philip wrote: >> >> Web2py is to me the next generation of MS Access, and I mean that as a >> compliment. MS Access first opened up the world of database-driven >> applications to business people. With Access they could throw >> together a simple application to manage a database (CRUD and reports) >> without having to hire a developer or wait on their IT staff to write >> one. Web2py does the same thing. It is easy enough for a business >> user to throw something together very quickly and be up and running >> immediately. The amount of development expertise required is >> trivial. For a basic app, if you read the web2py book, you don't even >> have to understand more than the very basics of python. >> > > +1 > > I'm database developer (going back to DataEase for DOS and FoxPro, and the > IBM S/26) in need of a data-driven front end, and I see web2py as the > perfect tool for me. I have no desire to tinker /inside/ web2py - I just > want to use it to develop apps. > > Rather than competing with Django /et al/, which are defined as much by a > culture as the technology, I'd like to see some advocacy to promote web2py > to people who simply aren't in a position to use Django, but who can get up > to speed with web2py very easily. > > The comment earlier about Massimo's approach being informed by his teaching > experience seemed very sharp to me. > >> For really, big complex apps, there may be some reason that Django is >> preferable - I'll leave that to the professional web developers to >> figure out the tools they need - but I can't say enough about how >> great my experience has been with web2py, as a non-developer looking >> for the "tools that in the easiest manner facilitate the creation of >> what I want to do" (to use your words). I just needed to get stuff >> done, and web2py worked. >> > > Just so. > > -- > > Cheers, > > PhilK >
