why not perl?

| | Comments (4)

I was recently asked this by a recruiter for ticketmaster (a big perl shop):

Quick question if you don't mind. Why not working in perl? You have perl in your background so it's always interesting for me to learn why people move from one language or environment to another. I hope you don't mind "sharing." ;)

My reply:

Perl sucks. Really. It is a horrifically bad language at expressing thoughts cleanly and clearly and from having a maintainable, well-engineered solution. I'm good at it (or was--I dunno about now, but hey, it's Just a Language (tm)), don't get me wrong. I've cut a lot of code in perl professionally and on the side. It just doesn't scale in the long term.

No... I don't mind sharing, as long as you don't mind me blogging it as well. :)

Interestingly, I ported the last of my perl packages to ruby last year. Despite not having worked on it for well over 4 years it was still readable!! It really does depend on the person, but if you're working for a perl shop... I guarantee that there's always that one person (or many) who writes that hideous noxious code.

No thank you.

4 Comments

"Perl sucks. Really."

That's classic!

I agree completely!

I think the best way to describe Perl's problems in a single sentence is, "Perl's whole mental model is broken".

Reading "Perl Best Practices" (esp the OO chapters) makes it clear enough what sucks about Perl.

Leave a comment

About this Entry

This page contains a single entry by zenspider published on May 11, 2006 3:17 PM.

ruby obfuscator is getting very very close was the previous entry in this blog.

"so simple it can't be wrong" is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Pages

Powered by Movable Type 4.32-en