Skip to content.

Manageability

Sections
Personal tools
You are here: Home » blog » stuff » re:

Comment

Above in this comment thread: Is Chandler's Demise Evidence that Dynamic Languages Can't Scale? » Wha? » re: » Sigh.

re:

Posted by ceperez at 2008-01-22 09:19 PM
You failed to read the reference I put up:

"But that’s hardly how it looked in 2002. It attracted people with considerable renown in the field, like Andy Hertzfeld and Lou Montulli, as well as other, equally smart and talented developers whose names are not as widely known. Nor, even at this late date, do I consider Chandler in any way to be definitively “doomed” — though certainly it has failed to live up to its initial dreams."

The project began with a lot of promise and was loaded with the requisite talent. It was in fact at the time to be a showcase of what Python was capable of doing. To mis-characterize it as just another Python project that failed is an attempt to deflect blame.

The book 'Dreaming in Code' describes events up to 2005. That was 2 years ago and is plenty of time to fix the projects mistakes. So, what happened since then isn't public knowledge and it's reasonable to question Python as a probable reason for failure. That's why my title ends is a question and not a statement.

Just to be clear, the project did NOT fail because of:

(1) lack of talent
(2) lack of resources
(3) lack of time

From what I've read from other sources, the project may have failed due to:

(1) Poor project management
(2) Poor team development
(3) Poor software practices

Claims that selecting Python was one of the few correct decisions would also be a stretch.

That's unless you provide some good arguments to back it up.
 
 

Powered by Plone

This site conforms to the following standards: