Stories
Slash Boxes
Comments

Slash Open Source Project

What would you like to see on slashcode

Displaying poll results.
more pointers to perl stuff
  25% 32 votes
more pointers to mysql/postgreSQL
  27% 35 votes
everything is just right
  7% 10 votes
more info on RSS
  11% 15 votes
more commnet on slash communities
  28% 36 votes
128 total votes.
[ Voting Booth | Other Polls | Back Home ]
  • Don't complain about lack of options. You've got to pick a few when you do multiple choice. Those are the breaks.
  • Feel free to suggest poll ideas if you're feeling creative. I'd strongly suggest reading the past polls first.
  • This whole thing is wildly inaccurate. Rounding errors, ballot stuffers, dynamic IPs, firewalls. If you're using these numbers to do anything important, you're insane.
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 Anonymous Coward
    A poll without cowboy neal is like ice cream without mustard.
  • by Anonymous Coward
    commnet on slash communities?
  • Oops, I should add that my comments about Slash are about bender, Slash 2.0, not Slash 1.0.x.
  • 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?

  • I'd like to see a scoop [kuro5hin.org]-style plugin. BTW, I gotta say the Scoop code looks a lot cleaner than the Slash code, just in the way things are broken out and it actually uses OOP instead of that getConstants, getUser, etc. goofiness. But Slash is way more powerful. I wonder how much cross-pollination is possible. It doesn't really seem like there are diametrically opposed goals.
    --

    --
    Deliberate with Coolness, Analyze with Criticism, Reflect with Candor.

  • The slashcode site has some great potential as a gathering place for admins of slash type sites. So far, imho, the best article I have read here was What it takes to Run a Weblog [slashcode.com]. It was informative and was actually the type of article I expected to see when I first started coming here.Things that would make this site a more valuable resource:
    • In depth looks at the way the code is designed (conceptually not blit for bit).
    • Tips and Tricks to getting feature 'x' working or modified.
    • Make YASS a section.
    • More Perl stuff
    • More mySQL stuff
    • Some 'How-To' features (setup/mods/pulls/culls of slash from other admins)
    • Articles on slash community development/building and marketing concepts (some very cool slash sites out there with almost no users and admins that are clueless about internet marketing)
    • Plug-In/modifications and integrations discussed (Some of the slash sites out there have done quite a bit of tweaks to the code, it would be great to discuss them!) or linked to for us to play with...
    • More Apache articles
    • How about a 'Where the F is X?' topic/section so newbie admins can ask silly questions and not feel like morons for asking them...
    All in all this is a good resource of information for those of us interested in running a slash based site. You guys have done a great job writing some awesome code and been kind enough to let us have at it. Slashcode is a good extension of that but it could be more. I can't say the slashcode site is bad about anything. I would personally like to see the article count per day go up a little (say 3-4 a day). I know not much discussion goes on in each article here but that does not mean we aren't reading them. As this is the 'official' resource for all things slash (short of sourcefourge) and the documentation of slash is kind of sparce, we really should discuss more stuff specific to installing, maintaining, and developing slash.
  • by Anonymous Coward
    Amen!