My first week of django - Reinout van Rees' website - The Diigo Meta page

• 10 Dec 08
  

  Olifante *

  A Plone veteran shares his impression after one week with Django.

  django plone comparison python webdev

  • Light-weight. That's really something completely different from the towering stack that is Plone. Change a .py file and django will just restart itself.
  • Simple customization mechanism, especially for templates. Basically what Plone had with the portal skins. With two differences that make it a bit more maintainable. (a) by convention, every add-on stores its templates in a subdirectory named after itself. So that does away with many name clashes and the one-global-namespace problem Plone had. Just a simple convention. (b) There's a list of template directories in the global config file. That's the order of directories in which Django searches for templates. I'd say that feels much more practical than anything that plone has right now.
  • 3 more annotations...
  • • Plone is much more out-of-the-box usable. That's a big advantage.
    • There's a field where plone (and zope3) play much nicer with the rest of the python world: easy_install. The 1.0 Django release isn't really on pypi.
    • Zope3 and Plone are actually closer to the rest of the python community than Django. Pypi is overflowing with plone, zope3, grok, buildout and generic eggs. If "we" need sql integration, we take sqlalchemy: Django has its own object-relational mapper that isn't used outside of Django.

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.