News for hackers. Stuff that matters.
Re:Programming is hard, let's go scripting.. by kamaal on Wednesday April 04, 2012 @12:31PM (#3798317)
Perl 6 has very ambitious goals. One aspect of Perl 6 is it pays extreme emphasis on sane, safe extensibility. Perl 6 grammars are killer features. For all those people who wanted lisp like extensibility inside C kind of a language, Perl 6 will be a perfect match.

Given those goals, Perl as a language has a long bright future. Because flexible and extensible languages evolve their way out of time.

Compared to all languages in its class, Perl hasn't broken backwards compatibility since past 25 years. Python had to break it for some very simple syntax changes. Perl has never done it, not even once in past 25 years. That is quite a feat considering so much syntax has been added to the language since then. Perl 5 has also found a way to add more syntax without dealing with the core by modules like Devel::Declare.

So Perl evolution is set for many years. You will see it evolve grow. New neat ideas and many like Moose will find their way into Perl.

Basically what makes it special is its hackable, flexible and extensible. And such languages generally stay around for a long time.

Re:Programming is hard, let's go scripting.. by zby on Wednesday April 04, 2012 @04:25PM (#3799662)
Back-compat can have many meanings - but my understanding is that every major release does break some back-compat in some way - otherwise it would not be a major release. And if you think that binary compatibility is not be fair - then how about pseudo-hashes?

This is not to say that I don't agree that Perl has perhaps the best back-compat of all the languages that still evolve - but these absolute statements have this slightly sect feeling.

Re:Programming is hard, let's go scripting.. by autarch on Wednesday April 04, 2012 @08:37PM (#3800668)
I think pseudo-hashes were always marked as experimental, up until they were removed.

That said, I'm pretty sure you're right that backwards Per 5 broke backwards compatibility with Perl 4 (and presumably 4 with 3, etc.)

Re:Programming is hard, let's go scripting.. by jleader on Thursday April 05, 2012 @02:07AM (#3801517)
From what I've read various places (but can't find a reference at the moment), the version bump from 3 to 4 was just to be able to have the Camel book coincide with a major version (i.e. "this book describes Perl 4" instead of "this book describes Perl 3.1.4.1.5" or whatever).
Re:Programming is hard, let's go scripting.. by masak on Thursday April 05, 2012 @07:33AM (#3802132)
Re:Programming is hard, let's go scripting.. by jleader on Thursday April 05, 2012 @04:53PM (#3804570)
Heh, thanks! I read through the whole thing very carefully before posting, and couldn't find it. Now I see it's in the Introduction: "Perl 4 introduced the first Camel book. Really. We mostly just switched version numbers so the book could refer to 4.000."