Speaking as a BioPerl core developer, I agree on a few points, in particular some of the over-engineered bits (and its Java influence). BioPerl classes designed 10 years ago are simply not easily capable of dealing with modern analyses for anything large scale.

However, I do wish that anyone who has complaints re: BioPerl would seriously consider helping to fix some of these problems, or at least offer suggestions; we're pretty short-handed. In an effort to make contributing easier, we've moved to GitHub (so anyone can fork the code), we're pushing out the last monolithic release soon (1.6.2), and we're about to undergo a major core reshuffling to modularize classes, so now's a good time to indicate areas that need improvement. A ground-up re-implementation isn't out of the question either, but I think we have to consider the problems with just tossing out everything and starting from scratch.

BTW, I know you don't believe in Modern Perl tools, but I do. I happen to have a test project using Moose to re-implement many BioPerl interface classes as Roles, as well as identify areas that need refactoring or simplification. I was pleasantly surprised to see a modest speedup just with Roles alone, so I think it's worth looking into.

In reply to Re^4: Putting Perl Back on Top in the Fields of Scientific and Financial Computing by cjfields
in thread Putting Perl Back on Top in the Fields of Scientific and Financial Computing by hermida

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.