in reply to Re: Modern::Perl
in thread Modern::Perl

A Modern namespace is bad, for aside from the problem you mention, it implies the standard is somehow antiquated.

If you only get implication from that, I haven't said it strongly enough. There is no good reason that the best features of the newest Perl 5 releases are only available to people who know the secret magic incantations to enable them.

This strikes me as a somewhat defensive reaction (marketing ploy?)....

It's not. It's an attempt to be somewhat less hostile to novices by encouraging them to develop good habits to write more maintainable Perl.

Stick with something less ambiguous and more to the point, I say.

The least ambiguous option I devised was Make::Default::Perl::Not::Suck, and that has its own flaws -- not in the least that it brings to mind dependency graph resolution engines.

Replies are listed 'Best First'.
Re^3: Modern::Perl
by Anonymous Monk on Jan 29, 2009 at 11:55 UTC
    #!/usr/bin/perlmodern
Re^3: Modern::Perl
by Arunbear (Prior) on Jan 29, 2009 at 22:47 UTC

    Perhaps a more emblematic name? TheSchwartz is already taken, so how about TheForce ?

    Or to borrow an idea from Class::DBI::Sweet, call it Perl::Sweet (Making sweet things sweeter).

Re^3: Modern::Perl
by Porculus (Hermit) on Jan 30, 2009 at 00:24 UTC

    IMO the best features of modern Perl are the things that are enabled by default without any special incantations at all -- things like // and named captures, things that actually make it easier to write readable code. In contrast, all say does is save a little typing. Explicit line breaks were never a maintenance problem like defined $8 ? $8 : defined $6 ? $6 : 1.

    (I guess given/when might turn out to be totally awesome, but I'm one of those people who never felt the lack of a switch statement in the first place, so I've not got round to trying them yet.)