The assertation is backed up by a quote from the original post by Naggum. I said "wrong" because you somehow missed that part of his post. He was not saying that Perl is wrong because it has some of Lisp's features. He was saying that it is wrong because it allows shitty work. In fact, it encourages it by making it harder to write good solutions.
Someone (Perl) can be beautiful (Lisp features), but that doesn't change the fact that they wear dirty clothing (ugly syntax) and they smell kind of funny (ugly solutions).
"The assertation is backed up by a quote from the original post by Naggum."
An ill-informed rant from a crank is not the same as "backed up".
"Someone (Perl) can be beautiful (Lisp features), but that doesn't change the fact that they wear dirty clothing (ugly syntax) and they smell kind of funny (ugly solutions)."
We all have our preferences.
While you can quote your favorite usenet crank from years ago, I can quote one of my favorites about Lisp (doesn't mean Lisp isn't a great language for many tasks...this quote just makes me laugh every time I read it):
"Lisp has all the visual appeal of oatmeal with fingernail clippings mixed in." --Larry Wall (larry@wall.org)
Smart people can disagree on many things. Programming languages are no different.
>An ill-informed rant from a crank is not the same as "backed up".
Omouse isn't (directly) asserting anything about perl. He's making assertions about Naggum's assertions. For that purpose, the ill-informed rant in question is an excellent source of corroboration.
Someone (Perl) can be beautiful (Lisp features), but that doesn't change the fact that they wear dirty clothing (ugly syntax) and they smell kind of funny (ugly solutions).