PS: And for years now I was asking myself if there is any robust decision process in Perl's planning ... doesn't look like.

I feel sympathy for SawyerX who, I'm sure, is merely trying to do the best thing for perl.
And if you're the "leader" of the organization, then it should be ok for you to make an executive decision without going through the long and dreary process of first consulting with everyone.
But, as soon as he does that, people start disagreeing with him and questioning his lack of pre-consultation.
I guess that, from my POV, an astute "leader" would consult first ... and then make the executive decision.

I find myself also wondering whether Larry's decision to rename perl6 to raku was a case of "doing the right thing by the perl5 community" ... or was it a case of providing the perl5 community with enough rope ?
I'm not saying that Larry is evil ... but I wouldn't be surprised if he's very shrewd.

Anyway, the arguments about what should be done to advance from perl5 to perl7 and beyond are somewhat over my head.
My aim will be to just deal with whatever gets thrown at me in such a way that my modules on CPAN work with all perl versions from 5.8 onwards.

Cheers,
Rob

---

---

• 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.