I guess the main problem is the future maintenance of Zope.
For instance, it is pretty sure that nobody will invest the time needed to
move it Python 3, and at some point it will probably be a problem.
On Wed, Mar 4, 2015 at 11:30 AM, Sebastian Tänzer <s...@taenzer.me> wrote:
> Hello ZOPE community,
> we're still developing websites using Zope2 + ZMS3 (www.zms-publishing.com)
> for years now and never ran into any real problems (compared to, let's say,
> Wordpress, typo3, Drupal etc. which had serious security problems over the
> years) and our clients are quite happy with ZMS.
> A few days ago on a barcamp the discussion lead to Zope and the usual
> comments, i.e. "Zope is dead", "I would not use that", "Too complicated",
> "Too old", "Outdated",.... and so on.
> My personal opinion is, that Zope2 is still rock-solid and gets the job
> done. I've never heard of any serious issues compared to the big
> competitors from the PHP or Java world. I looked into Pyramid and Django
> for different projects and always came back to Zope2 itself.
> I did not ask that question for quite some time now as there was no
> reason. Sure, sometimes we get comments like "never heard of it" etc., but
> nothing serious. Still, are there any specific reasons (beside personal
> favors) not to use Zope2 anymore? Any reason not to use Zope2 + ZODB for
> new projects? Are other frameworks like flask, Django, pyramid etc. that
> much better compared to Zope?
> Zope maillist - Zope@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> https://mail.zope.org/mailman/listinfo/zope-dev )
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -