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 ZM
Am Mittwoch, 4. März 2015, 11:30:30 schrieb Sebastian Tänzer:
> 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.
This is "stuff" typically spreaden by guys who d
That's a good question:
I'm not a Zope developer but I've been hosting several Plone sites
(including my own) for about 5 years now; and I am *extremely* happy
with the stability and security Zope+Plone offers.
Despite a couple of attempts by me, I never could start developing with
Zope. For me,
Hello Sebastian,
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.
Eric
On Wed, Mar 4, 2015 at 11:30 AM, Sebastian Tänzer wrote:
> Hello ZOPE
Am Mittwoch, 4. März 2015, 13:42:13 schrieb Eric Bréhault:
> 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.
This is just another such story which leads to non-interest of Users into Zope
and let me com
Hi,
I'm currently maintaining applications using Zope2, Zope3/Bluebream and Pyramid
applications (using ZODB).
I don't have any problem on any of them, even on the oldest Zope2 applications
which are more than 10 years old but always need zero maintenance and are as
stable as mountains.
But I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Bréhault wrote:
> Hello Sebastian,
>
> 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
