News for hackers. Stuff that matters.
Re:Desperate Perl Hacker by rjurney on Saturday July 24, 2010 @03:56PM (#1544270)
Comments like this seem to miss the point:

use strict; use warnings; is not required. Moose is not the default object system.

You can't say, "Oh, this library has that feature!" Thats not good enough. It has to be built-in, not optional, core to the language. If you're working by yourself - you can write code in any language well. In groups, that is NOT the case. Writing Perl in groups requires rigorous code reviews and cooperation, and even then nightmares are hard to avoid. Expressiveness has its downsides. You cannot simply bring a Perl noob onto a project and not have him ruin it. You CAN bring a new Rubyist onto a project and they can be productive.

Re:Desperate Perl Hacker by chromatic on Saturday July 24, 2010 @04:08PM (#1544282)
You cannot simply bring a Perl noob onto a project and not have him ruin it. You CAN bring a new Rubyist onto a project and they can be productive.

These assertions beg proofs.

Re:Desperate Perl Hacker by mmt on Saturday July 24, 2010 @08:35PM (#1544691)
* It has to be built-in, not optional, core to the language.*

This begs the question, what's core? Python's regex could go either way, for example.

Re:Desperate Perl Hacker by rjbond3rd on Saturday July 24, 2010 @05:30PM (#1544419)
Your requirement that certain features be "built into the core" seems to rule out a lot of languages which happen to be extensible.
Re:Desperate Perl Hacker by draegtun on Saturday July 24, 2010 @04:58PM (#1544357)
You can't say, "Oh, this library has that feature!" Thats not good enough. It has to be built-in, not optional, core to the language

CPAN is core to the Perl language and deliberately so. If you don't like this ethos then Perl isn't a "language" you should consider.