"J. Atwood" wrote:
I know this is probably a hot topic and will be much debated but have you guys at DC looked into this?
For a few seconds, yes.
Are there reasons why this is a good idea?
Few.
Bad idea?
Many. Java is not an open platform. Zope depends very much on the current CPython implementation. Java has 'stability' issues, depending on what vendor/platform/day of the week it is. No in-house Java expertise. Add to this the list of debatable reasons why doing anything at all in Java is a bad idea. The bottom line is probably that we don't trust Java like we trust C and Python. If Java sticks around for as long as either C or Python, then maybe I'll trust it a little, but never more than that as long as it is a closed platform.
It seems like a natural way to increase the performance of Zope while keeping all the power of OO and Python.
Increase? I think that's highly debatable. We could put just as much effort into increasing the performance of the CPython JVM or rewriting components of Zope in C and probably get a much higher performance return than depending on any one of a number of wildly different Java implementations to give us that. -Michel