Scheme and the Philosophy Behind Perl 6

Contrast Larry Wall‘s take on the “soon to be released” Perl 6 today [in 2008]:

Don’t design everything you will need in the next 100 years, but design the ability to create things we will need in 20 or 100 years. The heart of the Perl 6 effort is the extensibility we have built into the parser and introduced language changes as non-destructively as possible.

(via Computerworld)

with that of [R3RS] Scheme in 1986:

Programming languages should be designed not by piling feature on top of feature, but by removing the weaknesses and restrictions that make additional features appear necessary.

(via R3RS, referenced in R5RS)

In other words, language implementers ought to accept that they aren’t going to “get it right” on the first try, and they should leave the language extensible for additions.

Are you as excited about Perl 6 as I am! :)


4 thoughts on “Scheme and the Philosophy Behind Perl 6”

  1. Schema and Perl are my two favorite languages. I love that Perl has so many language features. It’s kind of a mess, but I’ve never found it confusing. A lot like English in that way.

  2. Chris Dean: I like to use Perl for scripting at work; but I’ve never taken the “deep dive” and learned it in depth. Perl 6 just sounds so exciting. I would say that can’t wait; but I’ll always have Scheme so I will be fine however long it takes to get released :).

Leave a Reply

Your email address will not be published. Required fields are marked *