For me, the main thing django has going for it is the free admin interface.  (Although, the URL mapping is pretty cool too.)

MWM

Components are more pluggable and replaceable than in Zope 2, and it’s easier to write reusable utilities and libraries and components than before. The Schoolbell calendaring application (a complete Zope 3 app) has a Relationship package that can be used to specify complex inter-object relationships. A very handy package on its own. The Zope 3 Base Project has a few interesting projects, including a SQLObject support lib for using SQLObject based objects in Zope 3, and there’s Hurry which provides some components writing easier catalog queries, doing simple workflow, and providing a file upload schema item and widget. On the high end of content management tool development, there’s the Z3ECM project at http://www.z3lab.org/

Note that the name for the Zope 3 project, as it was incepted in the Zope development subsite, was ‘Component Architecture’

Anyway, so what all those frameworks offer the same as Rails. There are not 1000 different ways of building Web framework, are they?

So what is the point of your article really?

"""What we need now, is a application framework. Something we can use to build website not webapp."""

Uh?! I don’t understand that either. Would you mind explaining it?

• Sylvain

Subway integrates FormEncode too, has autocompilation of Cheetah templates, partial templates and simple authorization/authentication facilities. We are also integrating Django-like filters with Cheetah. Subway aims to reduce boilerplate code as a mimimun — and i think it’s pretty good at that (compared to the rivals). Version 0.2 is finally coming into shape and will feature a stable API.
You can spot an example using MochiKit in the Subway SVN repos. Personally I have very high hopes for the MochiKit future.

We are also seeking developers to join the project, please join us instead to start your own. :)

– deelan.

• Manuzhai, you mean you can reuse your own code that’s it. But does Django support project sharing ? I mean does it have a standard way to look at usership, or access role, and so many other aspect of a website. Perhaps, I loose something but I don’t find this kind of stuff in the doc.
• Matthew, Phil, ok Django has a SCGI support that’s a good news, but only a part of the problem.
• Jeff, I work in a Zope company for a while, and (beside I forgot a big part) I know quite well Zope. For me Zope 3 has nothing to deal with Rails, but it provide some good Component Arch. Most products I tested for Zope 3 are buggy and Zope 3 isn’t stable enought to use it in company products. Not talking about the docs ..
• Sylvain, this is the main argument for Django: We wrote this for a long time now. Ok and ?
• Deelan, please take a chat with TurboGears. I really think you should merge this too projects. The only difference is the templating engine, and yes filter in cheetah will rock!

Though, now that Eggs are all around, i guess this is a bit less important, but heh, Django was designed long time before Eggs

(Maintenant on sait qui de l’oeuf ou de la poule etait le premier :)) )