comment on

I've been thunking about this on and off ever since I read the news item and referenced blog entry. And I have vacillated back and forth between the three positions:

An incremental (evolutionary) development path of a reliable stalwart.
A revolutionary leap that builds upon, but is not constrained by, that stalwart.
A future that favours useful and user-friendly enhancements to, (and where necessary), departures from, over backward compatibility.

I'm done thunking; I favour option 3.

And I suggest that "Perl5 v2" is a better nomenclature than the alternatives. And that what is currently designated as "perl 5.10.1", be re-designated as "Perl5 v2". And that the enhancements that currently require enabling be the default; and that they should require explicit disabling to retain 5.8.x backward compatibility.

And that the facility to so disable, be deprecated immediately, with withdrawal muted for "Perl5 v2.1" (currently designated "Perl 5.12.0"). All releases between now and (as currently designated "Perl 5.12.0") Perl5 v2.1, would be nomeclatured as "perl5 v2.0.x".

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re: Perl 5.10.0 or Perl 5 Version 10? by BrowserUk
in thread Perl 5.10.0 or Perl 5 Version 10? by xdg

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.


more useful options
	PerlMonks