Friday, July 02, 2004
rsslib

My good friend Cameron has released an early version of his rsslib package, a library of python code that makes RSS generation easier.

Check it out.

9:38:46 AM    comments ()  trackback []  

chandler redux

I wanted to respond to one of the comments to my post yesterday -- I'll quote what I want to respond to. Tthe original, full post is on the previous entry.

Quote: "1. There is no real end-user functionality in chandler 2. The GUI sucks or at-least-doesnt-impress 3. Nobody ever cares about good sourcecode ALONE. Or: sourcecode that doesn't deliver end-user functionality is obsolete."

Okay, point by point:

"1. There is no real end-user functionality in chandler"

Of course not. It's a Developer release. Says so right at startup, and on every page that leads to a download. Obviously you expected more. Sorry about that. It's a developer release, meaning that it's only of interest to people that want to develop for or with Chandler.

"2. The GUI sucks or at-least-doesnt-impress"

See the answer to #1. It's a DEVELOPER release. Of course the GUI sucks, it's a framework, with enough support to see interesting developer type things, like browsing the repository. Parcels are supposed to provide the GUI to manipulate their data, and all the currently exists are example parcels for developers. Sense a theme here? That's why they called it a developer release.

"3. Nobody ever cares about good sourcecode ALONE. Or: sourcecode that doesn't deliver end-user functionality is obsolete."

Of course not. They care about what source code can do, or what they can do with the source code. And how can you say that the Chandler code isn't delivering end user functionality? In order to do what they want to do, they need a good repository. It's the absolute heart of what they are trying to do. And so they are concentrating on that part.

Is this a version number confusion? I know a lot of open source projects aren't at 1.0 by the time they hit a good level of functionality. I never liked their versioning scheme, I think the first feature complete post-beta release should be 1.0.

Do I wish Chandler was farther along? Why certainly. Of course. I always want things to be done more than they are.

But you know, I also see a group of good developers (just look at the track record of the people working on the project. Now, just like they say in the securities business, past performance is not an indication of future returns, but if I was handicapping this race, I'd certainly bet on the team that has the record that the Chandler team has.

I keep coming back to this -- It's an 0.3 release, people. Personally, I like to cut projects a lot of slack until they get to the Beta releases. Until Beta, they aren't claiming to be feature complete, so complaining about features that are missing in a pre-beta release just misses the point.

8:56:54 AM    comments ()  trackback []