Stories
Slash Boxes
Comments

Slash Open Source Project

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • by pudge (6) on Tuesday February 27 2001, @12:06PM (#222) Homepage
    I'd like to see a scoop-style plugin

    What does that mean?

    I gotta say the Scoop code looks a lot cleaner than the Slash code, just in the way things are broken out

    Hm. From just the raw code itself, it looks about comparable. As far as the cleanliness of the API, it has some advantages; the Slash API is a bit hard to follow. We've done a lot of work on the Slash API, and we'll do more in the future (moving even more out of the Slash module, maybe breaking up Slash::Utility into other modules, etc.). However, as far as separating database code from display code from logic code, it is in pretty bad shape. It is about where Slash was a year ago in that regard.

    and it actually uses OOP instead of that getConstants, getUser, etc. goofiness

    Why, in Larry's name, would OOP be better? It would give you no advantages over the current system, that I can think of. There's no point in adding complexity and overhead by making that OOP unless there is a specific need for OOP, and I don't see one. Maybe I am missing something ... ? I don't want to get off on a rant here, but this OOP-for-OOP's sake sentiment is something I vehemently disagree with. Maybe that's not what you're saying though. Maybe you see a speific reason why OOP would be better. I don't know.

    It doesn't really seem like there are diametrically opposed goals.

    I don't know; what are scoop's goals?