We also had an online training about binding C-libs (the first online training that I know of), but it was not recorded. Perhaps we should do so and put it on a youtube channel...
And at that point they found out that Perl 6 will be a complete rewrite and not just a cleaned up Perl 5. I also guess that the Second System feeling already arrived in some minds, the problem IMO is more that the 'by Christmas' joke has been kept alive for so many years, without specifying a year.
1) Just update a little step by step. Here you would keep your userbase until there is a piece of software after a decade that will take a high percentage of that userbase.
2) Do a rewrite that takes three times longer than planned and split your userbase in half for the old and the new version. You can just pray that the new version is worth it.
So in a sense you will do the wrong and the right thing at once.
That really depends. If you need a richful module ecosystem then you won't be that lucky. But if your task would be doable with the many built-ins (and the modules shown on modules.perl6.org), then I'd say use it.
I see that I am way more expressive and faster to solve tasks in Perl 6 then, say. Perl 5.
(Besides I have to hack PHP at work in many cases. rant!)
And yes, there are ppl who use it for production, but I am not sure that matters much when there tasks might be totally different to yours?
We also had an online training about binding C-libs (the first online training that I know of), but it was not recorded. Perhaps we should do so and put it on a youtube channel...