jakoblog.de

• Website: jakoblog.de/
• About: I blog about Perl.

Recent Actions

• Commented on Deprecated modules warn when they are used
  I unsuccessfully tried to use this module to mark my non-core module as deprecated. Yes, this module was created for core-modules only, but why? I have found no simple and obvious way to mark arbitrary modules as deprecated, so far....
• Commented on A couple of ideas for improving commenting/reviewing CPAN modules
  Yes, we all are lazy. Having to log in with yet another account is a barrier. Much reviews are brief and quick, so they could be written ad-hoc like comments in a blog. I don't comment many blogs which require...
• Commented on The Four Major Problems with CPAN
  See this MetaCPAN feature request from one year ago. The more scoring indicators to be used for ranking in MetaCPAN, the better. How about explicit statements like "I prefer module Foo in favor of module Bar" to be used for...
• Commented on Sexual Harassment?
  The author should have written a unit test instead if putting the question into a comment ;-) No, seriously: the only situation when this comment may be an appropriate joke is in an already existing relationship between Linda and the...
• Commented on How to Post an Article on blogs.perl.org
  How to you get an account to write an article on blogs.perl.org in the first place? I just logged in with OpenID and cannot find a link to create an article....

Comment Threads

• Brendan Byrd commented on The Four Major Problems with CPAN

  This discussion was held several times over the years. A solution INSIDE the CPAN package is pointless here. For one: It doesn't address anything about EXISTING packages, which are 99% of the problem, new modules are rarely having these problems. So next, if you mandate definition inside the META file, then someone will NOT do it, or do it wrong. What you have then? RIGHT, the exactly same state then before.

  Calm down. Some of the ideas are META improvements, but I think the bulk of the fixes would be the first two ideas: search engine improvements and better ways of handling…

• larryl commented on The Four Major Problems with CPAN

  @brian d foy said:

  > I am constantly and consistently surprised about how many
  > people do not first try to work with existing projects.

  For me, GitHub has been the single biggest factor in lowering the barriers to entry to making contributions to existing CPAN modules. I find I'm far more likely to contribute changes to an existing module when all I need to do is fork it and send a subsequent pull request. Maybe if more source code was handled via GitHub (or similar mechanism) there might be less of a tendency to reinvent the wheel as opposed to enhancing existing co…

• Buddy Burden commented on The Four Major Problems with CPAN

  Yet Another Problem with the ideas (not that I wish to discourage you--definitely keep pursuing these ideas, as they're much needed--but just to make sure you're thinking of all the issues) is that, while sometimes there is a "right" and a "wrong" module, sometimes there isn't. That is, sometimes there are two modules that both do the job and there just isn't a clear reason to prefer one over the other. Perhaps one is OO and the other isn't. Perhaps one has more features but the other has a simpler interface. Perhaps one works well for A but not at all for B, while the other…

• Aristotle commented on Deprecated modules warn when they are used

  warn __PACKAGE__, " is deprecated. Please use Better::Module instead.\n"
      unless state $have_warned++;

• brian d foy commented on Deprecated modules warn when they are used

  I thought that was weird too, but I think the point of deprecated is to remove things from core. They might be perfectly fine and still supported, just not a part of Perl.

  Many authors, including me, have been lazy about specifying core dependencies because we always thought they'd be there. Now we'll get warnings about that, but only for core modules.