On Wed, May 15, 2002 at 05:06:27AM -0400, Scott Lanning wrote: > Something I'm wondering about is why a Zope-like > application framework (or whatever the buzzword) > wasn't built for Perl.
One thing to keep in mind is that a system can be built in one language but designed to be extended with another. Apache is one obvious example of this. They built a server that was extensible in C at most of the places that would be useful, then mod_perl was created to stick a perl API in front of those useful places. For a while WebObjects seemed like another system that had a distinction between the implementation language and the extension language, but it wound up that it quickly went from "extensible in Objective-C", to "extensible in Objective-C and Java" to "extensible in Java". A bit later you deride Tcl, but when Tcl was created, it was a good example of this philosophy as well. It was designed to be a simple configuration/scripting language bolted onto a larger, more useful program. So I would suggest to not look at the implemenation language of an extensible system, but rather look at how the system is designed to be extended. With zoperl, Zope methods can be written in perl. Very little of what was shown last Tuesday was python code. It was the Zope management interface and templates. For the chat application, we showed how it hooks up into zope, but the essence of the chat code itself probably could have been written in either language. -- "Daddy. The Powerpuff Girls aren't fighting. They are saving the day." -- Samantha Langmead, age 4 1/2.
