perl

Just to get the chronology straight, Perl 4 was released in 1991; the first Perl 5 was released in 1994.

And even if perl's implementation isn't stable/good, it doesn't mean the model of explicit sharing is a bad one.

Much larger, and the overhead pushes my 4gig machine into swap (so perl's not very efficient with its data overhead, it seems).

If you have to install two different shells for their functions, why not just use a real scripting language like Perl or Python?

I suppose something had to be invented to make bad perl look crystal clear.

People keep pulling me back to Perl though.

On top of that, creating a single thread takes 15 seconds because Perl is spending a ridiculous amount of time copying the entire state to the new thread.

It seems like 5 years ago there was lots of solid web dev work happening in Perl still and now it seems like a sea of Rails and Scala/Java.

Last time I used ithread it made Perl crash and burn.

I've been wondering what's happened to all the Perl devs.

I've spent the last 13/14 years writing Perl so I started getting worried a year or two back that I was making myself unemployable by not branching out.

(Go read the net.legends FAQ.) And Perl wasn't a great language before 4, in 1993, and didn't attain anywhere near peak popularity until 5.

Which had killfiles.) Perl came into being in 1987, which is before September 1992, so his creation of rn must have had traction/worship before the "Eternal September." I'd hardly say that said event was the reason that people worshipped him for rn, especially since Perl was out for ~5 years at that point.

You can now simply argue that this is Perl's way to manually declare a subroutine call as tail optimized (i.e.

I used to do this stuff in Perl, and have been using Python more recently.

Compare that to Unix/C/C++ (or Lisp, Smalltalk, Perl, Python, Ruby, etc) that were created by programmers for programmers.