Deployment
- I want it to be easy to deploy Perl6 apps in places where only a minimal Perl6 runtime exists, and little else.
- I'm hoping Parrot gets fast enough that I'd need to depend on fewer c libraries than I do today.
- I want standard module management tools.
#1 and #3 are somewhat at odds? Sometimes I'm wishing the runtime would have a centralized registry of installed modules; but sometimes I want each app to insulate itself from the possible harm of others installing/upgrading modules. The system has to know how to have two versions of the same modules installed, and I have to learn how to use that effectively. We should lift the good things from Java (PAR++!) but avoid the bad ones (Multiple JVMs on the same machine--!)
Dialects, refactoring
- A core tool that gracefully degrades source code to ASCII ('»' → '>>' etc.). The other way 'round might be fun, but is less important.
- Once upon a time I wanted a 'use stricter' pragma for Perl 5 I could use for pedagogic purposes. I hope I get that in Perl 6, though I'm not holding my breath.
- Oh, I want to resurface the idea of a fully decorated AST from which you can reconstruct source code, including comment and whitespace. This is immensely powerful for IDEs (credit to BrowserUk).