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.

They Call This a Softball Question in Interviews 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Here's my list of reasons why:
    • Refusal by the ruby-core team to implement a real test suite.
    • Refusal by the ruby-core team to implement continuous integration.
    • Refusal by the ruby-core team to ever go back and refactor any of the core C files.
    • Continued use of pre-ANSI C. It's 2008.
    • Refusal by the ruby-core team to compile with any warnings on, ever.
    • Terrible release management by the core team. Community built spec suite failures ignored.
    • Addition of questional libraries into the stdlib.
    • Cowtowing to the

    • I agree with your entire post, including the subject. I don't believe that people outside the Ruby community who have a negative perception of Ruby hold those reasons though. For all of the technical problems of Ruby (and the only one on my list and not yours is questionable but fixable implementation decisions), perception is primarily a social problem.

      (For similar Perl problems, see comp.lang.perl.misc and Perl golf.)

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.