Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Damian … said it's "already too late."

I agree. I have no clear idea how a rename will help anyone at this point unless the porters decide to release the next update as Perl 7 the same time the rename happens. But still, without some significant marketing dollars spread around—and maybe an extremely good app or two—it will harm more than help. There will be no differentiator in the release, unless signatures and some OO become bombproof, non-experimental core. The widespread, entrenched hatred for Perl 5 will commute directly to Perl 7 with newly strengthened critiques: look at this mess, it hasn’t changed, it’s just a trick, the upgrade cycle will kill everyone’s apps, as if Perl had any apps, compatibility is impossible with a double version jump, talk about your backpedalling! et cetera, et cetera.

And FTR I still disagree, strongly, that Perl 6 hurt Perl 5 particularly or in the grand scheme. Perl 5 was circling the drain *beforehand*. That was the entire genesis. Perl 6 caused some confusion but less division of effort than claimed and it brought back-ported improvements and renewed interest. Without that, I don’t know that Perl 5 wouldn’t be in worse shape today.


In reply to Re^11: Ovid's take on the renaming of "Perl6" by Your Mother
in thread Ovid's take on the renaming of "Perl6" by 1nickt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (5)
As of 2024-04-23 16:14 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found