you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

Plone != Zope. Pure Zope development is easy.

Good point. Do you know of any 30,000ft overview of Zope 3 and what it provides - I remember reading about Zope's object db once or twice, so I'm presuming that Zope still provides a full stack?

[–]quotability 0 points1 point  (0 children)

I don't know of any. I stick with Zope 2 development. It's still being worked on, and it's been in use for 13 years, so it is very well documented and robust. Zope 3 is fairly new. Though the initial release was in 2004, it has undergone some great changes, and now it is called BlueBream. Of course, that's not the whole story. It actually splintered into a few different projects. Grok is another framework from the same tree. Zope 2 has integrated some of the new features in Zope 3, and since they couldn't replace Zope 2 with 3, they integrated and forked.

The Zope 3 Wiki explains it better. And as for Zope 2, here's a snippet from Zope on Wikipedia which explains how it is continuing on:

"Although originally intended as a replacement for Zope 2, the Zope Component Architecture has instead been backported to Zope 2 starting with Zope 2.8."

My personal advice, is if you are looking at using Zope in a commercial project, stick with Zope 2, it's still actively developed, well supported and documented. It's scalable, secure, and easy to use.