comment on

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.

In reply to Re^2: Modern::Perl by chromatic
in thread Modern::Perl by metaperl

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Clear questions and runnable code get the best and fastest answer
	PerlMonks