If you think that no one in the Java world welcomes the move, think
twice.
Indeed, it would be wiser to make implications from that piece of
information first, instead of focussing on "my implications", which
to be honest I doubt many people care much about..
But to dispel some doubts about some points that obviously got
misunderstood:
Zope3 needs an IDE, in my opinion. Zope2 had one (the ZMI) which
allowed you to create an application and which most non-expert users still
use as a way to customize their site. So why does this simple assertion has
to be tackled from a binary perspective
on "the IDE vs the language"? that's not the point really.
Zope3 needs a stable API, in the sense that it needs to
stabilize some time.
Valid reasons for wishing one's users to migrate to the new API include:
the old API is insecure, buggy, or highly inefficient
the old API is going away in a future release
the old API encourages very bad coding practices
in other terms there should be real reasons for deprecating, not
simply because the code needs to be restructured or refactored, or
packages be moved from zope.app to zope, otherwise it really
gives the impression that the code isn't ready.
ZCML is not XML. Because in an XML configuration file it is possible to
put several levels of nested elements. In ZCML there is place for
directives and for subdirectives (2 levels). That forces you
to add indirections in the ZCML file itself to fit 2 or more levels in your
file.
...
self-cricitism, well, I am sure that you know what I meant
already, I probably don't need to be more explicit :-)
