However, I think we should also take a long, deep breath, and try to veer the discussion toward what can we do to improve the situation. For most (if not all) of the organizers, YAPC is a labor of love. And labor is the right word there -- it's a long, arduous, exhausting, unglorious process that end in a big final week-long push. Personally, I have no doubt that everybody involved honestly did gave their all. But life, and things, and then more life, happened. And as King Leonidas could attest, even with the mightiest of intentions an heroic few can only do so much.
So, what I'm trying to say, I guess, is: let's thank the organizers for what they did. Let's recognize that there are areas that need improvement. Let's discuss openly about what can be done to make things better next year. Let's ensure that things do indeed get better by perhaps lending a hand. And let's never lose track that YAPC is, when all is said and done, is not something existing outside of the community. It *is* an ephemeral incarnation of the community. It is us. Its long-term success, or its failure, is totally up to us. All of us.
]]>http://www.gnubila.com/geas/g-platform-as-a-service
P.D. The G platform is enormous. And now they want to GPL it, but don't know how.
]]>
pkgsrc.se seems to be the home of NetBSD packages. It has a search functionality that helped me locate the page for Expect.pm and another one for IO-Tty.
In there I could not find any code changes for Expect.pm (all the changes seem to be to the NetBSD Makefile).
For IO-Tty I found this entry that seems to indicate there is a patch called: pkgsrc/devel/p5-IO-Tty/patches/patch-Tty.xs
]]>Bingos has an open pull request here on the IO::Tty repo:
https://github.com/toddr/IO-Tty/pull/3/commits
It seems however the patch is unrelated to your problem?
]]>spawn id(5): beginning expect.
Timeout: 1 seconds.
Current time: Sun Aug 3 06:58:41 2014
Waiting for new data (1 seconds)...
spawn id(5): new data.
spawn id(5): read 6 byte(s).
23+7
Returning from expect successfully.
spawn id(5): accumulator: `+7\r\n'
not ok 1
# Failed test at 02-bc.t line 28.
# got: '23'
# expected: '30'
Closing spawn id(5).
my @new = map { s/foo/bar/r } @old;
Compared with the old way:
my @new = map { (my $tmp = $_) =~ s/foo/bar/; $tmp } @old;]]>
It is not that difficut to include instructions for those who want to port their CGI scripts.
Something like
sudo cpan CGI
will do the trick ;)
I think Perl can move on and remove CGI.pm from core modules.
What it is really missing in the core, in my opinion, are IO::Socket::SSL and Plack.
Look at Node.js core, for example http://nodejs.org/api/tls.html
We need https!
Simple terminology issue. On cpan you can release a dist as either indexed (stable/normal) or unindexed (usually denoted via an underscore and a number at the end of the dist version.) I had always seen people call these unindexed dists alphas. I had assumed that was simply the term for it on cpan. I always thought it was funny that there was alpha, but no other designation.
Your comment prompted me to take a look and ask around. Turns out un-indexed are not simply called alphas, which makes more sense. Mistake on my part, I will update my post to change the terminology, and I will no longer call them alphas.
]]>