Dan Wright will give a talk at YAPC::NA 2012 described as:
Perl events come in all shapes and sizes ranging from tiny hackathons to a full-fledged YAPC’s.
In this talk, I will cover various lessons learned from years of running Perl events. I’ll reveal some often hidden pitfalls and outline methods for success in running your event. I will also cover some of the resources that are available to help you run your event.
Audience: Perl experience isn’t really relevant to this talk. This talk is suited for anybody that has an interest, but little experience in event organizing.
Bio: As a founding organizer for The Pittsburgh Perl Workshop, I know first-hand what it is like to run an event for the first time. Since 2006, I’ve organized 5 PPW’s and a YAPC. Currently, I am planning for PPW 2012 and also serving as Treasurer for The Perl Foundation.
It is time to talk about Booking.com. I hear many people ask about us and guess what it is like. I hear lies. I hear truths. No one will really tell you. I will tell you and I wish be fair. Booking.com may be very good for you, but you need to know before you take job if you want it. Booking will tell you the good stuff, not bad stuff.
I will not mention names. I don't want to cause people trouble, but I see good people being pushed out door. This makes me sad because there is no hope of getting better. First, I talk about code.
Before I talk about code: remember that Booking has become the number one in what they do. They are making piles of money and are still growing fast. They are doing something right. I will sound upset about some of this, but some of what they do is good. They are very smart people.
I may be the last person to do this, but I finally put all of my conference slides, and a few of my presentation notes, on slideshare.net.
It was fun going through my old slides. I started giving presentations at ApacheCon in 2000, where I gave a talk with Bill Hilf about our work building eToys with Perl and open source tools. The article version of that is online, and the slides add very little, so I skipped that one.
I also skipped my Perl ORM talk from 2005, because the tools I covered are not really relevant anymore. I would advise people to look at Rose::DB::Object and DBIx::Class now, not Class::DBI, SPOPS, and Tangram.
Unfortunately, I can't see a way to sort the presentations so that the newest ones are first. If anyone knows how to do that, I'd like to hear it.
One amusing thing I've discovered: putting the word "scalable" in your title seems to draw in a lot of viewers!
If you requested a payment from the Perl Foundation recently, you may have noticed a little bit of lag in receiving your check. Or, a very few of you were even unfortunate enough to have received a check and then asked not to cash it. Here's what happened...
"Much of what looks like rudeness in hacker circles is not intended to give offense. Rather, it's the product of the direct, cut-through-the-bullshit communications style that is natural to people who are more concerned about solving problems than making others feel warm and fuzzy." - Eric Raymond
Torsten Raudssus will give a talk at YAPC::NA 2012 described as:
Talk about DuckDuckGo and Perl. The application and infrastructure of DuckDuckGo and about the Open Source and GreyPAN movement. Also giving an overview how to contribute to DuckDuckGo. Good for beginners to dive into Perl and contribute to a real world service directly.
Every time I use perldoc for any term slightly unusual, I struggle. Have you tried to use it to find UNITCHECK? Now you can. Instead of remembering which of these to use (and none of these will find UNITCHECK):
In the last case above, the --all is needed to do a brute force search. Ordinarily, you just do perlfindsearchterm, regardless of whether it's a module name, function, variable, or faq keyword and it will return the first result found (searched in the order I just mentioned). Otherwise, it will tell you to use --all if you really want a brute force search to find out where that term is used.
Here's a gist I tossed out there. Patches welcome. I should bundle this up and put it on the CPAN (and handle older perldoc versions).
I mean creepy in the sense that results slowly creeping in. People who follow my tweets know that 2 smaller milestones are achieved: predefined subrules and regex quantifier are now all in place (in Index A and B). This was of course a byproduct of my upcoming Perl 6 Regex and Grammar talk.
So we not far away from 700 items in Index A (50 more than last time). Some bits other were done.
Hope you guys are not to impatient but since im doing this thing for years and still on it, its not far fetched that one day im ready with it. It's also like writing a book, which, when taken seriously, needs constant improvement. The quality and consistency of the entries grew all the time. They also explain some of the terms like LTM, role, runtime and so on. if you think that doesn't have to be in an index, please let me know.
When it comes to
user experiences with Marpa,
I confess to being a highly biased source.
I hope the following observations
will be useful nonetheless.
(Marpa, for those new to this blog,
is a new, powerful and fast parser and parsing algorithm.
To learn more,
check out its web page.)
Marpa does the job
If you've read user's accounts of work with BNF grammars over
the years
(I have studied many),
you know they follow a familiar pattern.
The user has some BNF.
He then tries tool X (for X substitute
yacc, bison, PEG, recursive descent, etc.)
and finds that it almost works.
Almost, but not quite.
The rest of the account describes the user
beating up his grammar in an effort to make
it fit the tool.
Perhaps 50% of the time, he reports that his effort
was wasted.
I’ve worked out a deal with University Housing for the dorms for YAPC::NA 2012. They’re now accepting reservations for Sunday, June 10th in addition to the weekday reservations. This should help those of you who are coming in for the workshops or hackathon. Register for your dorm now, or update your existing reservation.
I have high hopes for this module as a tool to help authors provide the C libraries they need through CPAN far more easily than hand rolling an Alien:: module. As such I feel a deep urge to ensure that Alien::Base is robustly tested.
Unfortunately I’m finding that testing such a module is rather hard. Alien::Base is a very abstract concept. It only makes any sense when it is used as the base class for some other Alien:: module, and futher, THAT module is only fully realized when it is used by some other module which needs that C library.
Graham Knop will give a talk at YAPC::NA 2012 described as:
In this talk I’ll talk about the massively multi-player video game written in Perl known as The Lacuna Expanse. I’ll talk about how and why it was built (some Perl internals). And I’ll also tell you a little bit about Lacuna’s achievements.
With over 120 developers in our teams, based in London and Cluj, Evozon offers custom software solutions, business analysis and project management across the widest possible range of technologies and platforms for web and mobile. Our clients rely on us for innovative bespoke or platform-based solutions.
Of our over 120 strong team in Cluj-Napoca, Romania, over 20 are full-time Perl coders that have in-depth experience developing Perl – using a wide range of frameworks. These technologies include mod_perl, Mason, Catalyst, Moose, DBIx::Class and Class::DBI with MySQL or PostgreSQL all architected in a high availability and scalable model with the best practices one would expect. Evozon also supports Perl by sponsoring and participating in YAPC Europe, London Perl Workshop and some contributions to CPAN.
The former is complicated, but suffice it to say TB2 cannot rely on Mouse or Moose or Moo. It's being solved by writing an OO compiler, something which will generate accessor methods and roles at build time rather than relying on a runtime compiler. This should also solve TB2's less than ideal startup time. It might be Mite or it might be Moo, but the problem is being taken care of.
The second is harder and is what I call "Test::Builder2 vs CPAN". Because Test::Builder has been around or so long, and so much depends on it indirectly, there's a lot of not entirely documented behavior being relied on. We've been using CPAN modules as a broad test suite right along for this reason. TB2 has the potential to seriously break a lot of module's test suites, so it's best to get it as right as possible before stable release.
