I have kept silent on this issue while watching comments fly by.

I'll agree with a comment Paul made about passions being high and that
can be a good thing. Disagreements are sometimes inevitable, however we
do not have to be disagreeable.

It seems that many here who do not share the concerns of others have
left technically arguments and gone on to calling others childish or
silly. It is reasonable and understandable that you may not agree with
them. However to resort to such behaviour is below this community.

I hope the concerns expressed by many here do not happen. However, that
does not mean they can't. I like many here chose Python then Zope. I
chose Python not Perl.

What is taking place here and has caught many in the community off guard
is somewhat of a change in what Zope is. Some have expressed that Zope
is already multilingual. That is true to a certain extent. But Perl does
not add to Zope capabilities that Python does not have. (IMHO) In this
perspective it does not add to Zope.

Python, DTML, SQL, XML, XML-RPC, XSLT, etc. are not equivalent
languages. They have different scopes and capabilities. Python and Perl
are reasonably equivalent in capabilities and it boils down to personal
preference on the choice.

This brings us back to a change in what Zope is or what Zope has been
seen as. This provides an opportunity for DC and the community to really
define what is Zope. This discussion needs to clarify what Zope's
definition is. This will promote greater understanding and reduce

To this point in many peoples minds Zope has been defined as being
Python. This changes things. Yes I understand Zope itself is built in
and will continue to be built in Python and C.

This is a paradigm shift for many here. Once this settles down, I hope
this community will be stronger for it.

More comments to follow.

Jimmie Houchin

Zope maillist  -  [EMAIL PROTECTED]
**   No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-dev )

Reply via email to