Comment
Above in this comment thread:
Is Chandler's Demise Evidence that Dynamic Languages Can't Scale? » Rumors of Chandler's Death Are Greatly Exaggerated
visitors
reading
This site conforms to the following standards:
And if the various fiefdoms can't agree on whose component model to pick, pick a foreign one. For example, just pick OSGI or the Eclipse plugin model and then move forward.
The Pyhton community is very innovative. However the downside is that there's too much of a N.I.H. syndrome. I mean, Zope was the equivalent of Rails (i.e. the killer framework) for the Python world. Anyway, what happened to Zope? Appears, everyone and their mother decided to build yet their own other web framework.
Carlos
A lot of things happened, and are still happening, to zope, see zope3, buildout, repoze, grok. Is the fact that people are able to build their own web frameworks relatively easily meant to be a criticism of Python? :) There is much to criticize in Plone and Zope2 architecture, and Zope3 and newer Plone versions solve many of the problems that earlier versions have. None of those problems were inherent to python, they were mostly due to the fact that Zope was pioneering a lot of ideas, like the way it uses an object database for web publishing, and acquisition (a double edged sword, everyone agrees by now.) No one gets it right the first time. The fact that there actually is a second (or third, really) time, goes to show that there is enough of value in Zope for developers and users to stick with it.
Also Plone != Zope != Python, and you having problems with your blogging software is somewhat anecdotal, certainly not grounds to condemn the language the framework that that software was built on, was written in.
Replies to this comment