I think the reference is to the software development method called "put together a Perl prototype as quickly as possible, then hope they like it well enough that they use the prototype and we won't have to recode it in a real language."
Not that I've ever been connected with such a project, of course.
LISP is a programming language that is notoriously difficult to understand, not because of it's inherent complexity, but because it is radically different from other languages (it's based on reverse Polish notation, so you have to type things like "+(2, 2)"). It has a bazillion parenthesis. I've never actually used it.
Perl, on the other hand, is a fantastic language for hacking things together. Frequently back-end systems are ostensibly actually designed and written in some language, but the perl "glue" code often used to connect different components on Linux/Unix servers ends up doing all the work.
6 comments:
Uh, I thought I was a computer geek of sorts...
but I don't get it.
Heresy!
It was Fortran.
Perl? You are so geeky :)
I don't get it technically either, IC. But somehow it still struck me as funny.
I think the reference is to the software development method called "put together a Perl prototype as quickly as possible, then hope they like it well enough that they use the prototype and we won't have to recode it in a real language."
Not that I've ever been connected with such a project, of course.
LISP is a programming language that is notoriously difficult to understand, not because of it's inherent complexity, but because it is radically different from other languages (it's based on reverse Polish notation, so you have to type things like "+(2, 2)"). It has a bazillion parenthesis. I've never actually used it.
Perl, on the other hand, is a fantastic language for hacking things together. Frequently back-end systems are ostensibly actually designed and written in some language, but the perl "glue" code often used to connect different components on Linux/Unix servers ends up doing all the work.
Post a Comment