Perl 6 Language Design Tablet: Revision 20
Larry Wall: You should not take this picture to mean that linguistics is the opposite of common sense. But ehm, there are many computer scientists, who have complained that it should be more like engineering and less like an art. And I disagree. But thats oukay.
Enjoy Life and enjoy the freedom expressing yourself. Which means: support you as much as possible and not to force you in any way. Perl 6 likes to be, even better than Perl 5, your humble servant for translating your thoughts into binary code (if possible).
Every style and level of expertise has to be supported and even more difficult: all of them have to play together well. The default often imitates a natural language (i.e. english). Strategies and concepts for this are coined in several often repeated terms.
The everlasting slogan:"There is more then one way to do it.", meaning: your way is valid too. Only be aware of logical consequences.
All your paradigms belong to us
We learn/take/adapt from every source possible to offer the best of all breeds. And you should be able to keep your style when switching to Perl. Some of the paradigmes are structured, object oriented, aspect oriented, functional, design by contract, declarative and logical.
This term is an extention to the last one. Not only every programming paradigm but also every technique or neat trick loudly markeded out there as "must have" "in the [%DATE%]", should be available in Perl 6 (or at least be possible) as long there is productive value in it. "named parameters", "lvalue subroutines", "parametrizable subclasses" or "hygienic macros" are just a few.
Keep easy things easy and hard possible
Beside TIMTOWTDI, the other ancient slogan. Even if nearly every cool idea is crammed into Perl 6 we don't loose track of the simple basics like read a file (with slurp and lines simpler than default P5) or print to the command line (got with say also simpler in most cases). Rule of thumb: if you can think of an concept as trivial, than it should be. And if you can think of a computable solution, it should be at last doable in Perl.
That's a refinement of the last rule. It means that all the common, often used things have short straightforward names. The more verbose indicate less used, harder to grasp concepts or things that overwrite the default rules ("weird things should look weird"). It also implies that the defaults are leaning toward what a beginner/non-perl 5-programmer might expect ("hide the fancy stuff").
Waterbed theory of liguistic complexity
The underlying philosophy of the two term before. All Perl words should reflect logical units which you can combine freely. Make it more complicated than necessary is obviously not aspiring. But oversimplification will create artificial complexity somewhere else. Like an waterbed where you can push somewhere your hand in but the water will go up another spot.
Second system syndrome
Less Unix Centric
Perl 1 was a child of the Unix world, borrowing a lot of folklore and words. As Perl 6 had to regularize the Regex and reform some other part, this heritage has become less visible.
In Perl 5 we had my, our, use, require, bless, can, ISA (is a), chop and also of course if, else, goto and all the loops. Perl 6 adds given, when, take, WHERE, HOW, WHO and lot more everyday english which should make it easy to read.
High order functions, currying, you name it. All that goodies are there, as Perl 6 aimes to an full support of functional programming.