I'm going to talk about that which I know very little, but looking at the Perl6 Module Directory, I see a namespace that's already storing up pain. Why are there so many modules in the top level namespace that make no sense for a language that has designs on world domination? I can believe that in the early days of development there's an intoxicating freedom to give your module a snappy name, but didn't we learn these lessons 20 years ago? What happened to Noun::Adjective::Adjective as the guiding principle?

If you're determined to re-invent the wheel, at least try to invent a better one. - Camel Book, 2nd ed. p277. footnote on False Impatience.

Let's unfairly single a couple out. Chess Why is this not under the Games space along with Druid? I'm not saying that there should be hard and fast rules about what's allowed in the Top Level, but if you browse through CPAN, the reason for choosing descriptive names should become obvious after a while. This is something that people agonize about on the module-authors mail list. Don't you want people to use your module, rather than duplicating it out of ignorance? How are they going to find it when the module directory starts to page? Plan for a very big future or there won't be one.



On a separate and mostly unrelated rant, I see some people denigrating Perl6 as people's "hobby language". (it wasn't dagolden, but flashed past my eyes sometime in January)

What's so wrong with having a hobby and getting excited about it? The best thing in life (next to crushing your enemies, seeing them driven before you and hearing the lamentations of their support staff) is to be paid to do your hobby someday, n'est-ce pas? Now, I'm not going to stop writing Perl5 any time soon, but I am going to learn the new language eventually by gradually porting my old modules over, ready for the time that the Bug takes off. Looks like fun.

Like the advert says - Be more dog!