All the Perl that's Practical to Extract and Report

Navigation

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Without JavaScript enabled, you might want to
use the classic discussion system instead. If you login, you can remember this preference.

Here's what you're missing: Perl 6 and "good stable threading in perl 5" are not mutually exclusive. It's not as if the people working on Perl 6 would necessarily working on your pet projects. Fact is, Perl 6 is not at all a distraction from Perl 5. If anything, it's feeding Perl 5.

Let me insist: trying to build Perl 6 is less useful to real, practical perl than actually working on Perl 5. If you think proper OO syntax, multithreading, better speed, etc are "pet projects" of mine, then we really have nothing more to discuss, since I believe those are major issues in perl 5 that should have priority over perl 6 work. You can't expect me to believe that the perl 6 team can't work on that.

Also, I think the point which is lost is that the users aren't clamoring for a "lexically overridea

If there's anything I really want or need, I can work on it, or start my own project. All I'm trying to do is send a message, after many years of contemplation. Again, I am not alone, and the issues I mentioned are real and don't affect just myself.

I know it's hard to accept, but since the RFCs, perl 6 has pretty much been a lost cause. Also, I don't value someone's work just because someone sweats or holds weekly meetings. There's only three things I care for: delivery, delivery, delivery.

No, I'm not part of the problem. I'm just some guy. I have no obligation at all to fix the Perl community or to make it work how you want, and I'm probably unqualified to do so. I'm as much a "part of the problem" as my three year old son is. I am completely uninvolved, other than commenting on this web forum. I'm just trying to assist you in clarifying what the people you are talking to in thinking. If you don't like my assistance, you can have a complete refund.:)

--J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers

...since I believe those are major issues in perl 5 that should have priority over perl 6 work. You can't expect me to believe that the perl 6 team can't work on that.

You seem to be operating from an assumption that most of us working on Perl 6 would instead be spending our time and energy on Perl 5 if Perl 6 didn't exist. The question is not whether we can work on Perl 5 major issues, the question is whether we'd be motivated to do so.

Halting Perl 6 development today will not cause stable threading in Perl 5 to appear sooner than it otherwise would. Neither "stable threading in perl 5" nor the other features you've mentioned are blocked because of Perl 6 development. As far as I know, none of the existing Perl 6 developers are at all interested in working on these featu

Well, if I can help... I've given this issue some thought in the past and can put together a wishlist of what *I* think would be useful. Of course, it's just my opinion, but stealing from a few other langs.

Well, if I can help... I've given this issue some thought in the past and can put together a wishlist of what *I* think would be useful.

Oh, that would be terrific! The ideal place for such ideas would be on the perl6-language mailing list. I will be honest up front that sometimes discussions and threads on that list quickly become bikesheds and messages get initially warnocked, but all of the thoughts and ideas that enter that list do get noticed and consideration from the core design team. Not everyth

I have reconsidered, after reading where the logo came from, and how only a person or two gave the idea of getting professional help a second thought.

The discussion on the list is not the sum-total of all discussions on the topic -- it has also been discussed on IRC. Several more than two of us have floated the idea of using a professional designer -- we just didn't use the mailing list to suggest or discuss it.

And fwiw, I did get a professional designer to come up with the temporary logo for Rakudo.

By which, do you mean the part about larry suggesting it feminizes Perl?

... I also take it as a given that we want to discourage
misogyny in our community. You of the masculine persuasion should consider it an opportunity to show off your sensitive side.:)

I remain in utter awe of the whole thing....have the entire lot of folks gone off their meds or something? Women who survive in this business will not be seduced into thinking a language with a feminine butterfly must be a lot less full of assholes tha

Well, I don't know that professionalism or a well-formed plan is always so needed, especially in the original spirit of opensource but, to anyone who thought P6 was, or has become, a joke by way of 8 years of design will not be dissuaded from that position by that site. It might even persuade many others who were merely neutral into thinking the language has reached it's comic endpoint.

And no, a man who can't confront the people who make perl an unfriendly misogynistic place will not get a pass with a fluff

I didn't say "infinite" I said "unbounded." You have a scarcity point of view, and I see the world as abundance.

You're ignoring the three points of the post, and carrying on the idea that if only Perl 6 didn't exist, you would have what you want in Perl 5. There is simply no reason to believe that.

What I see here is someone who's just very angry, and that anger is all you can bring to the table. Rather than understand and accept the help from numerous people (me, Patrick Michaud, etc) who have tr