It's a list of projects all loosely oriented around untying Perl 5 the language from perl the runtime. Perl 6 has already done this, with several (Parrot, JVM, Mono/.NET) VMs currently working fairly successfully, if a tad slowly still.
Personally I'm most excited about perlito (which features perl 5 compiled to javascript, among other things) and p2, which promises to be a super-speedy rendition of Perl 5 based on why the lucky stiff's last public project, the Potion language/VM.
The idea, as I understand it, is that if both Perl 5 and Perl 6 are running on the same VM, they can share library code on the level of that VM's bytecode.
All of that said, perl the runtime remains actively maintained and improved. End Perl users are just going to have some choices, much as Ruby users have had for a while (JRuby vs MRI, for example).
For the folks who struggle with Lua's language design: try thinking of it like Crockford's Good Parts of Javascript with a slightly different syntax (and arrays/objects rolled into one, the table). Generally speaking, once you've moved past the default indexing from 1, that analogy works out pretty well -- even down to how to set up more object oriented designs (js prototypes and Lua metatables/metamethods are rather closely related ideas).
LÖVE is a very fun engine, much easier than PyGame to get going - in both setup and development terms.
Indexing from 1 and 0 seem to me to reflect two different equally valid viewpoints. Offsets against a base address in memory (the C family) versus labels for boxes (Lua and friends). Naturally, stating from a base address, the offset is 0. Equally naturally, if you're labelling boxes with numbers, you number the first one "1". For Lua, given the tables are also at the same time hashes (with explicit labels), treating them as numbered boxes makes sense.
I think also the construction of the for loop makes it more natural. Lua is "for i = i, n" vs the more complex and off-by-1 prone "for (i = 1; i < n; i++)" where you need the less than vs an equality.
Personally I'm most excited about perlito (which features perl 5 compiled to javascript, among other things) and p2, which promises to be a super-speedy rendition of Perl 5 based on why the lucky stiff's last public project, the Potion language/VM.
The idea, as I understand it, is that if both Perl 5 and Perl 6 are running on the same VM, they can share library code on the level of that VM's bytecode.
All of that said, perl the runtime remains actively maintained and improved. End Perl users are just going to have some choices, much as Ruby users have had for a while (JRuby vs MRI, for example).