in reply to Choosing modules - community matters or just technical merits?

This is timely -- last night at the Perlmongers meeting we had a presentation on Rose::HTML::Form, and six months ago we had one on Rose::DB::Object.

After the first Rose presentation I was intrigued, and looked at the IRC channel #rdbo -- there were, I think, three people there, and I put Rose back on the shelf. The presenter last night commented that John, the author, was amazingly helpful on the mailing list, and that the documentation was 'fantastic' -- so maybe I need to have another look at Rose.

Certainly Toolkit::Template Template::Toolkit was a bit of a leap when I started using it -- but the documentation was very good, and there were enough people using it here on Perlmonks that I could get by. I tried DBIx::Class about a year ago and couldn't understand it -- the users on the IRC channel (and in particular mst) tried hard to help me, but I couldn't get it in the time I had allotted.

I think it's always a good idea to be tinkering with something new -- last night's meeting has suggested not only Rose but also SQL::Abstract. And I may take another swing at DBIx::Class, especially if I can compare it with Rose.

Update: Correct the name of Template::Toolkit. Thanks alexm. (Dyslexia sneaks up on you sometimes.)

Alex / talexb / Toronto

"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

  • Comment on Re: Choosing modules - community matters or just technical merits?

Replies are listed 'Best First'.
Re^2: Choosing modules - community matters or just technical merits?
by perrin (Chancellor) on Feb 01, 2008 at 19:17 UTC
    The support for Rose::DB::Object is fantastic. Very helpful author and plenty of other contributors on the mailing list.

    There may be some kind of generation gap with IRC. To me, it seems like a horrible way to get answers to tricky technical questions: no useful archive, tons of noise, and a general time sink. However, other people obviously like it.

    I'd recommend skipping SQL::Abstract and using the query builder from Rose::DB::Object instead. It's generic and can be used to build more sophisticated SQL than SQL::Abstract.

[reply]
        The support for Rose::DB::Object is fantastic. Very helpful author and plenty of other contributors on the mailing list.

      That's what I heard .. and the speaker last night did mention he'd started to see some postings on jobs.perl.org asking for Rose .. that's always promising.

        There may be some kind of generation gap with IRC. To me, it seems like a horrible way to get answers to tricky technical questions: no useful archive, tons of noise, and a general time sink. However, other people obviously like it.

      Going to an IRC channel for technical support is a bit of a leap of faith. I visit #perl irregularly, but enough that I know and avoid the idiots, and also know who the knowledgeable folks are. Not unlike seeing Congress or Parliament in action, I suppose -- there's a lot of talking going on, but surprisingly, some of it is significant and meaningful. It's even a bit like fishing .. some days, you get lucky, and some days, the fish just aren't biting. Not that I have the patience for fishing. Sailing, yes. Fishing, no.

        I'd recommend skipping SQL::Abstract and using the query builder from Rose::DB::Object instead. It's generic and can be used to build more sophisticated SQL than SQL::Abstract.

      Coming from you, I'll buy that. Looks like there's no yum package, so I'm running CPAN to install it. Thanks for the feedback.

      Alex / talexb / Toronto

      "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds

[reply]
Re^2: Choosing modules - community matters or just technical merits?
by alexm (Chaplain) on Feb 01, 2008 at 16:50 UTC
[reply]

In Section Meditations