Re: Wanted: Opinions on Logging Frameworks

[Discipulus]

I associate in your same question being curious to ear other monks experience and opinion.

I just would add Log::Contextual to the list: infact when I wonder, as you, about some module I firstly check what is in Task::Kensho list.

Before other wiser monks add their experience I can say that if you already have a good experience with Log::Log4perl I see no motivation to quit it.

As everytime it depends on what ou need and what you expect by using a module. And it relates on the cost of importing a, possibly large, framework into your application.

You can also be intersted in some link I collected on my cell

L*

[learnedbyerror]

Thank you for adding Log::Contextual. It is an interesting module.

I really appreciate your mention of Task::Kensho. I don't think to look there enough :(. As I somewhat expected, I found Log::Log4perl and Log::Dispatch; however, I was surprised to not see Log::Any. That makes me wonder if Log::Any may be an idea that hasn't had the uptake that I would have expected given its authors.

I have bookmarked your cell - Very, Very Interesting!

Thanks!

lbe

[perlancar]

As Task::Kensho admits itself in its documentation: This list is by no means comprehensive of the "Good" Modules on CPAN. Nor is this necessarily the correct path for all developers. Each of these modules has a perfectly acceptable replacement that may work better for you. This is however a path to good perl practice, and a starting place on the road to Enlightened Perl programming. I agree that Log::Any is one among some modules that really deserves to be there. I'd even suggest that it replace Log::Contextual instead (Log::Contextual is a weird choice, it's not particularly interesting and far from widely used.)

All in all, I view Task::Kensho as an opinionated list of recommended modules. I'd encourage people to publish their own list also.