Damien "dams" Krotkine

• About: I blog about Perl.

Recent Actions

• Posted MooX::LvalueAttribute - Lvalue accessors in Moo to Damien "dams" Krotkine

  cross-posted from dams blog

  MooX::LvalueAttribute - Lvalue accessors in Moo

  Yesterday I was reading Joel's post, where he …

• Commented on Perl 7
  @dolmen : For me, Perl 6 has not failed at all as being a next generation language. But it's not anymore "the next Perl". It's a different language. So it should not be in the Perl namespace. Or so I...
• Commented on On the version number succeeding Perl 5
  Joel : I don’t see why using year in version means dropping backward compatibility. That said, I think yearly version naming is probably better suited for “distributions” (be it Linux, or anything that is a bunch of packages). I would...
• Commented on On the version number succeeding Perl 5
  I would definitely add in the list of things to ship in Perl 7: include Moo or Moose by default. I think it’s very important to have a proper object system available without having to install it from CPAN. My...
• Commented on Perl 7
  Yes, Many linux distributions have switched to year related version naming (Mandriva, Gentoo come to mind). Perl 2013.1 for first (or second, depending if we start at 0) quarterly release. Sounds nice to me....
• Commented on Perl 7
  I agree with Joel Berger, I vote for Perl 7, and Perl 8 not too long after. I don't see why Perl 5 should continue suffering from Perl 6 diversion anymore. One of the 2 languages should have his name...
• Posted New Perl module: Action::Retry to Damien "dams" Krotkine

  cross-posted from dams blog

  New Perl module: Action::Retry

  I've just released a new module called Action::Retry.

  Use it when you want to run some code until it succeeds…

• Posted Mass-Testing Dancer's Plugins to Damien "dams" Krotkine

  cross-posted from dams blog

  Mass-Testing Dancer's Plugins

  So, as I said at YAPC::EU 2012, one thing that remains to be done before Dancer 2 can be released : migrating the plugins, making sure they work with it.

  To be able t…

• Commented on Paris.pm technical meeting
  I'll try to get them online and publish them here...
• Posted Paris.pm technical meeting to Damien "dams" Krotkine

  cross-posted from dams blog

  Paris.pm technical meeting

  ( french version below )

  The next Paris.pm technical meeting will happen the 25th september 2012, with:

  • Elizabeth Cholet: Firefox automati…
• Posted MooseX::Singleton is slow to Damien "dams" Krotkine

  cross-posted from dams blog

  MooseX::Singleton is slow

  Just a quick note : if you plan to use MooseX::Singleton, beware ! It is easy to use and it implements properly what i…

• Commented on YAPC through the eyes of a recruiter
  It's nice to see recruiters' point of view, we need more of that. Out of the blue, do you have any idea for promoting Perl that could be done on the recruiter's side specifically ?...
• Posted Dancer is community-driven to Damien "dams" Krotkine

  cross-posted from dams blog

  Dancer is community-driven

  Long time I haven't blogged about Dancer.

  Antelink is a french startup, specializing in Software Life Cycle Management and Open So…

• Commented on Explaining Web Programming via Plack
  "Plack is intended to be a platform one builds on, not uses directly" : exactly. Plack is probably an excellent choice to introduce the Web mechanism with a good balance between very low level and too high level. That said,...
• Commented on whack-a-mole
  Hm, is it really better than running Perl::Critic with Perl::Critic::Policy::Subroutines::ProhibitExcessComplexity policy enabled ?...
• Commented on Cross Posting to blogs.perl.org
  @Barbie : I'm not sure if we've moved into a parallel reality, but I can't find the Web Services Password page anymore ! Maybe some admin tweaked the permissions and the page is not available anymore ? I'll try to...
• Commented on Cross Posting to blogs.perl.org
  Aha, funny enough, we can see that the cross poster failed to handle properly the image. And the code block could be better. Is it possible to do nice code highlighting here ? if yes how?...
• Posted Cross Posting to blogs.perl.org to Damien "dams" Krotkine

  cross-posted from dams blog

  Cross Posting to blogs.perl.org

  So, a while ago, I moved my blog to github, using jekyll and ="http://daring…

• Posted Paris.pm january technical meeting to Damien "dams" Krotkine

  Cross posted from my github blog post

• Commented on The First Test I Always Write
  Same here, I let Dist::Zilla handle everything generic, tests among other things. So you can concentrate on writing useful tests, targeted at your application features....
• Commented on I will (probably) be attending the French Perl Workshop!
  That's good news ! It'll be a lot of fun, especially if you can stay for the Dancer hackathon on sunday (I think). If you need a place to crash, you're welcome to stay @ my home....
• Commented on More Ouch
  @ JT Smith : Try::Tiny pod explains why it's important to localize $@. The DESTROY example is especially important, as it's more common than on might think. http://search.cpan.org/~doy/Try-Tiny-0.09/lib/Try/Tiny.pm#BACKGROUND Ouch's implementaion of try() is not good enough for me to use...
• Commented on Perl is Dead (to bing.com)
  Well, from here it works well. The results are not as good as on google, but it's showing perl related stuff definitely. There is a link to the "Pearl is dead" search query, but that's all. Maybe you've enabled some...

Comment Threads

• arrestee commented on Perl 7

  There's a problem here that I don't see being discussed. "Perl7" or "Perl2013" or "Perl Foo" is a fork, plain and simple. The 5.xx line will not end just because somebody decides to evolve Perl5 into something not quite compatible with what it was. There will still have to bug fixes, which means maintainers, which means itches to scratch and ideas to try. In short order, we will have Perl v5.2x, and Perl6, AND Perl 20xx.

  Stevan Little already explained that one of the reasons he decided to build from scratch with Moe is that there's a serious shortage or surgeons qualified to o…

• Wendy commented on Perl 7

  Perl 6 already has Rakudo with a monthly release cycle with year and month in the name. At the moment we can all work with Rakudo Star 2013.01 and work is being done on 2013.02.

  Renaming Perl 5.20 to Perl 7 and skipping Perl 6 is throwing away man-years of work, energy, inspiration. Just talking about it might demotivate everybody in the community of Perl 6 developers.

  Many people are not interested at all in Perl 6, even not knowing that enormous efforts are made to make Perl 6 more and more backwards compatible with Perl 5, and giving Perl 6 more features that people are w…

• CosmicNet commented on Perl 7

  I believe that such action would be a real nail in the coffin. After all the talk of Perl 6 being the language of the future, people see a Perl 7 release, think "Wow lets take a look" and Perl becomes a laughing stock when they all see it's just a patched Perl 5. What's worse this would jeopardise Perl 6, and all that's gone into it. I think a better title would have been "How to wipe Perl out for good with a simple version number change" or more simple "The Perl 7 one liner of death".

  Perl 6 is the future, an I firmly believe it'll fix everything. If people are impatient then the so…

• Matt S Trout (mst) commented on Perl 7

  As an alternative idea - how about we pick a name rather than getting even further into the numbers game?

  See my blog post on the subject for my suggestion as to what to pick.

  -- mst, out

• Ether commented on On the version number succeeding Perl 5

  I can see not wanting some warnings to be fatal, but it’s so rare to need to disable certain warnings entirely (e.g. numeric) that I’d be firmly on the side of keeping them enabled.

  Another change one could make in such a release is to do all the things tchrist lists as needed for full unicode and utf8 compliance: http://stackoverflow.com/a/6163129/40468