mdipierro

If you have questions you gave a very active users group: groups.google.com/group/web2py

It is biased since I made it but I have emailed people I know from other frameworks and I have incorporated all the corrections that they have sent me.

after you create the db connection db=SQLDB(..) you need to write session.connect(request,response,db=db). can we please move this discussion on the web2py google group?

perhaps you should try the online demo: http://mdp.cti.depaul.edu/demo_admin and read this: http://mdp.cti.depaul.edu/examples/static/web2py_vs_others.p...

I disagree with your criterial of looking at previous qualifications of the developer but by your own criteria you should love web2py.

Yes, developing the ORM was very very easy compared to, for example, developing www.fermiqcd.net (BTW we should be friends since I see you are in data representation and me too these days mdp.cti.depaul.edu/vqcd).

I will agree with you that for some of the web2py components there is a better module out there, the point you are missing is that the web2py modules are designed to work together while the alternatives are not. You will not appreciate this until you try it. Here is an example: Pygments is a much better general purpose syntax highlighter than the web2py's one, nevertheless web2py's one can highlight web2py code, create clickable links from web2py keywords to the web2py online documentation, is faster and fits in 10k. If you need to syntax highlight Java or PHP code you can still easy_install and use Pygments. Although you can, the web2py modules are not designed to be taken out and used separately.

SQLAlchemy is better than the web2py ORM in dealing with legacy databases. web2py has restrictions in this case. But the web2py ORM is much better integrated with the rest of the framework than SQLAlchemy is integrated with, for example, Pylons or TurboGears. If you do not use the entire web2py framework you are better off with SQLAlchemy. If you do use web2py, you are better off with its own ORM. Here are some preliminary benchmarks (take them with grain of salt) http://mdp.cti.depaul.edu/AlterEgo/default/show/76

Please do it, to my email or to the web2py mailing list. they will be taken care of or you I will explain to you why I disagree with you.

Three other people came to pick up the rules and some more were on the mailing list, were supposed to and didn't. I spent 24 hours coding and felt like a fool when nobody else delivered. You are taking a quote I made to my users' group out of context. Why do you turn a discussion about some work of mine into a personal thing?

Being a professor who teaches the stuff for a living and grades other people's work, you remind me of that typical PhD student that knows enough to talk about his work but nothing enough in detail to ever graduate. No offense.

Let me add that in life is the new things that give you an edge, not those things that everybody knows.

I updated the document and listed 3. When the other two come out I will update it again. Thanks.

Can you make any specific point so that it can be addressed or are you just ranting as usual? Who is doing marketing here? Since when computer science is about faith?

I just made many corrections. I could find only 2 published books. please send me a personal email if you have other corrections and they will be incorporated.

"enterprise" does not mean it is developed by an enterprise. It means it was developed for the enterprise. For one thing it means it is stable and always backward compatible. It also means it packages everything you need including support for xmlrpc web services, file streaming, if_modified_since, partial content, distributed transactions, ticketing system, etc.

The Flourish conference was sponsored by Google. The creators of Django, CackePHP and Rails were on the mailing list and some even replied to it. I agree that if nobody else participated it is not a victory. I would not say web2py won, I would say web2py was not afraid to participate and delivered a working project in 24 hours that met the specs. The organizers said web2py won. Ask the organizers. Ian Biking was on the jury.

Thank you aitoehigie. :-)

Are you still upset with web2py because I did not include your package. Com'on. Grow up. web2py is a project grown in a university, it is all but marketing. Unless free good documentation is called marketing. Here is the latest draft manual: http://mdp.cti.depaul.edu/examples/static/web2py_manual.pdf Here is a preliminary comparison with other frameworks: http://mdp.cti.depaul.edu/examples/static/web2py_vs_others.p... (please correct me if I am wrong)

This funny because when web2py started we aimed at being small like web.py. In fact the core web2py functionalities (from gluon import *) are very similar to web.py and the entire core is less the 120KB. Ocan still use it that low level and import SQLAlchemy and Mako for example (with loss of some of the higher level functionalities of course, like the database administrative interface).

Anyway, I agree with Cosmin's assessment that it grew to do a lot more. The main phylosophy is that the framework should make (by default) some decisions for the user, in particular particular about things that have to do with security and persistance.

At high level web2py borrowed some ideas from Django (the administrative interface and {{...}} in templates), some from Turbogears (response.flash?) and some from cherrypy (@cache).

If we want python to take over java, we need to speak "their" language. Seriously, why don't you give it a try and tell me your impression? It takes 10 minutes.

True: compiling is obfuscation, not encryption but, the same argument applies to Java, VB, etc. Even compiled C++ can be disassembled. Anyway, web2py inlines some stuff before bytecode compiling so if you decompile a compiled web2py app you do not get a valid web2py app (because there is no one to one match between modules) unless you tweak it. In most of the cases it is not worth the task.

web2py used to be called Gluon so it is new but not too new. The main reason for bytecode compiling in web2py is that, for each page, the template+layout+included views are converted into a single bytecode compiled file. That means that when serving the page there is no parsing of the template, no pattern matching, no text replacement and therefore it is much faster than the alternative.