Rakudo and NQP Internals Workshop (14/15 Sep)

Perl6 is at a turning point. Now running on 2 virtual machines (Parrot and JVM), with 2 more coming available in the next months (Javascript and MoarVM), with abstract concurrency on the JVM now and full Perl 5 interop at the horizon in MoarVM.

To make it easier for past, current and future Perl 6 contributors, we have asked Jonathan Worthington to give an intensive 2-day workshop taking a deep dive into many areas of the Rakudo and NQP internals. This is your chance to get up-to-date with Perl 6, specifically with Rakudo and NQP.

The workshop will mostly be focusing on the backend-agnostic parts but with coverage of the JVM and future MoarVM backends too. While the overall focus will be on getting to know the Rakudo and NQP internals, we'll also build the odd small language and object system along the way to get a better handle on the primitives.

It will be held in Frankfurt am Main, Germany, on 14/15 September 2013

Perl Reunification Summit

As some of you may know, my partner Wendy van Dijk and me organized a Perl Reunification Summit on the Friday and Saturday before the YAPC::Europe. Organizing this started in May already, when I tried to contact as many people face to face to discuss this, before finalizing the plan. When the plans more or less got final, I basically sent this email to the people I had not been able to contact personally yet. Since it explains a lot of my reasoning for having the Perl Reunification Summit, I thought I’d share this mail with you.


As of April this year, I’m on indefinite sabbatical. So I have time to worry about other things than $work. And I worry about the future of Perl.

I see several developments that may be in themselves good, but together may spell the end of Perl as a significant programming language. And since I’m very egoistic, I would like to be able to continue to program in Perl in the future. For fun. Or for whenever I would need to / want to get out of my sabbatical and make money in a fun way.

The good things I see are:

  • all of the new developments in both Perl 5 and Perl 6.
  • a regular release cycle of both Perl 5 and Rakudo Perl 6.
  • many new contributors in Perl 5, and some in Perl 6.
  • a lot of people working on Moose and MOP.
  • hackathons being organized and making a lot of good things happen, that would otherwise would have taken much longer.

The not so good things I see are:

  • little communication between communities, other then stealing each others ideas and implementing them slightly differently.
  • a generation gap between older and newer contributors, mostly in Perl 5
  • further divergence between Perl 5 and Perl 6, will they ever meet?

The thing I really miss is attention to being able to use all cores of a CPU, in both Perl 5 and Perl 6. Perl 5 will never be able to transparently support multiple cores, Perl 6 still has the promise of being able to do so in the future. I think this support will be vital to the future of Perl, to prevent it from going the way of MS-DOS in a Windows environment. It will work nicely in a window, but will look (and be) old-fashioned. And not using all of the available resources.

So I wonder, will the more or less dwindling user base of Perl 5 (compared to other programming languages), and the as yet almost non-existent user base of Perl 6, ever get enough traction to make it possible for anyone to keep making a living with Perl? In other words, if we’re adding Perl 5 and Perl 6, I fear we’re going for a situation of ½ + ½ = ¼, rather than a situation of 1 + 1 = 3.

This is the moment therefore, for me to throw the proverbial coffee cup against the wall. But with a twist this time. Because I have an evil plan.

Since I have the time and the resources at my disposal, I would like to call a summit to discuss these matters with a group of about 20 people just before the YAPC::Europe (on Fri 17 and Sat 18 August). I tentatively call this a “Perl Reunification Summit”. It will be held in Hotel Perler Hof in Perl, in Germany, close to the Luxembourg and France borders. It is close to Schengen (of the Schengen Treaty), which to most Europeans means that they don’t need to be checked at the border anymore when going from one country to another. So I would like to think there will be some symbolism involved. But the name is not important.

What is important is that a group of “important” people from the Perl communities get together and talk to each other. And see where we go from there. Hopefully be able to create a vision for the future.


And so we got together. And talked. Talked a lot. In the whole group. In one-on-one’s. In small groups.

Over drinks, dinner, and just while chilling in the yard of the hotel late at night, when the temperature finally got bearable.

And we had some group mug throwing to expel the “Perl is dead” meme from our minds.

So what will the future bring? I wish I knew. It seems that we agree on the importance of being able to run (a subset of) Perl 5 on Perl 6. So several people are now looking at ways of doing that.

One approach would be to use Flavio Glock’s Perlito approach, which currently already builds an AST for Perl 5 and runs that on a Javascript backend (allowing you to run Perl code in your browser). Other approaches involve adapting Perl 6’s grammars to parse (a subset of) Perl 5, and thereby create a direct interface between Perl 5 and Perl 6. Other approaches are more general, such as MST’s Object::Remote (one end running Perl 5, and the other in Rakudo).

And what about me? I’m working on my first commitment now: to blog about the Perl Reunification Summit. If you want to know what’s going on, please check #p6p5 on irc.perl.org. And if you feel up to it: find out ways to support this effort to create the Perl of the future!

First Post

So, why don't you write a blog? A question I have been asked many a time in the past years.

I guess I mainly felt that I didn't have to tell the world much. And I was busy with $work.

Then you stop $work and start with $sabbatical. And start acting on the strange ideas that you developed over the years. Then you're asked to really start a blog this time. Really. And then you commit to that.

So here's my first post on blogs.perl.org. Not a lot of content yet. But it's a start. And more will be coming shortly.