Today I took a light rail with my son, to bring him to school. That tram is 90 years old. It has been maintained for 90 years. Milan city sold some of them to San Francisco too.
I have read http://www.manageability.org/blog/stuff/chandler-failure and I think it is very danger way of exposing concepts.
In the article pointed out, the quite dead Chandler project is compared to the multi-billion Eclipse project. And then a too easy analysis is done against dynamic languages, where Java is the absolute winner.
I will try to fix some of the things said there, and to add also my two cents here :)
First of all, I use Java a lot, but I am also a fan of dynamic languages. Every tool has its place in the world, and I will avoid some holy war here.
Anyway, it is important to understand major differences between very distant projects.
First of all, Eclipse is a very huge project, developed by IBM and based from the beginning with a very strong hype on plugin modularization.
The effort pushed inside Eclipse is very huge and come also from the San Francisco Project. Other IDEs (like JBuilder and Together) stops fighting Eclipse years ago, and eventually failed even to sell their stuff.
So there are no similar example to Eclipse in Python/Ruby/Perl world. Even in PHP is hard to find a so huge and well designed program. And the languge here is less important: a company big as IBM can also code in PL/I all its stuff, without so much pain :)
Second, PHP is very successful language, even if a bit too insecure, at the present time.
PHP Language has poor support for modules and so on, but project like Drupal, Joomla and other are full of plugins, quite easy to write.
RubyOnRails is falling down because nobody is understanding why PHP should be abandoned for Rails.
Java architectural model is very well written and Sun worked very hard to it. Java Hot Spot VM is derivered from the Self dynamic language, and has inside technology difficult to develop in an open source project.
Surely Dynamic languages are strong when there is the one-man-band paradigm: sharing works in Smalltalk was a bit complex in early days.
Put Perl, python and ruby have a strong modularization concepts, and so this issue is often solved.
I have tried Zope and I think it is weak because:
- Zope is user is non-existent. Zope user is a super-skilled web master which wants a web CMS without writing so much code.
- Zope product upgrade is a nightmare
- A stuck Zope Product can destroy your work. So hosting Zope is a problem
- A lot of Zope basic objects (like cache accelerators and so on) are poorly minded: they works only on RAM, and are not thinked well. Drupal 5 has more strong theory for this issue, and Drupal is poor PHP code.
- Zope use a proprietary database, when a simple SQL database with a relational mapper can do the same thing…think twice before reinventing the wheel!
- Every major Zope releases breaks a lot of the API. This is the most stupid thing you can do as open source developer.
Chandler failed because they tried a very difficult business: calendar software is a very difficult area to address. All operating system (including possibly C/64 :-) has now a huge set of Personal Information Manager software (PIM), and LDAP solves sharing issue for big companies
Even Ximian Evolution is near death.
And your bigger competitor is Microsoft Exchange and… yes… old Unix.
Dynamic lanuages has many lacks, and difficult refactoring is a problem but… remember frefactoring tools was INVENTED under SMALLTALK!
IT is a place where you must be careful… isn't it?