Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

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 | Reply
Loading... please wait.
  • I'm glad someone is coming out and saying it. I still don't [willingly] use M::B to this day because all of the bug/feature/change traffic on it makes me nervous. I know M::B is better than EU::MM. I know I should use it. But everytime I read about issues like this, I always head back to EU::MM because it just works for my needs, and I already have a level of predictibility with it. Add on top of that the fact that Catalyst switched from M::B to Module::Install and all of the app upgrade issues that came
    • M:B still scares me as well.

      M:I saw an increase in the number of users recently, and the addition of a new project member (me) and so there's been changes to try and improve the "approachability" of M:I.

      This has resulted in some bugs that were previous hidden being exposed. It also doesn't have very many unit tests yet.

      But in general, M:I should be usable, and at this point I'm quite ok with it. I use it for around 60 distributions.

      Yes, I'm going to have to do some upgrading of all these 60 because errors in older M:I are causing problems, but that's not so bad. At least it can be done safely, and modularly.