More than that. Three languages were chosen. One was based on what previous studies had shown works, and one sounds like it was basically a ROT13'ed perl (only with symbols), and from what some were saying on Reddit it was an overcomplicated dialect of perl (though IMHO that would change little). Then, in a study in which they pitted Perl against a language designed to do well in studies, the language designed to do well in studies prevailed.
Even though I do question whether there may be a wee whiff of tautology about this whole exercise, this is interesting because it shows that studies may be able to distinguish between the features of two languages w.r.t. how easily they can be taught and learned. This is valuable stuff, millions upon millions of dollars to society's worth of valuable stuff. What it says about Perl is simply that it was not designed to do well in such studies, quelle surprise, and in particular it doesn't say anything at all about Perl relative to any other real language. $YOUR_FAVORITE_LANGUAGE may well have fared worse, and $YOUR_MOST_HATED_LANGUAGE may well have fared much better.
It is a true shame that the underlying valuable message of the study is being missed by so many people in a tearing hurry to go "hurr hurr, perl t3h suckz, hurr hurr".
No, it's not surprising that perl performed poorer than Quorum. The surprise is that perl did as poorly as Randomo, which should not be sensible given that the operators and keywords are gibberish.
I generally agree with what you're saying, but the point of the study is not that the well-designed language did better. Who wouldn't expect that? But there is no tautological question when you realize that the result they are focusing on is the near-even performance with Randomo, not the failure to exceed or match Quorum.
It's pretty clear that they aren't engaging in perl bashing, but trying to provide data that backs up their experiential findings as teachers.
So, while it still looks pretty bad for Perl, I'd say it's not that bad.
Have you read the study? If not, you can find it here: http://www.cs.siue.edu/~astefik/papers/StefikPlateau2011.pdf
Additionally, i am not anonymous. Google my name and you will find all about me, including, if you look for longer than a minute, my full name and address.
Lastly, there was no need to give support in that comment by repeating what others and myself have said copiously all over the comments here. This was my main post towards that. Feel free to argue it: http://news.ycombinator.com/item?id=3153249
I disagree. If it says anything, it's that if you give bad code to people who don't know anything about programming, they'll have trouble writing good code.
The methodology may be sound, they may be good students and deserve a good grade, but there are absolutely zero conclusion to draw from this paper except for the fact that it may be valuable to make a larger study.
It is not The Final Proof (against what? perl?), but it is nice to find one way, among maybe other, to give some ground to empirical teaching experience.
I don't know much of perl, but I tried bash, and know PHP well, and really, really, the language used does matter, it will shape your models and logic, and change the way you handle, debug, write, read, maintain code.
Some people seem to adhere to the relativist cliché: all languages are good for something, in their field of usage. It is a matter of personal taste (implying it doesn't matter at all).
I don't agree. All languages are not equal. The breadth or their application field is often not comparable (eg compare bash, which is useful for some unix scripting tasks, with python, which can do web, and math, and stats, and windows grey-hacking, and multiplatform desktop clients, and image processing, and Unix scripting, etc.)
Having worked with (and fought against) PHP for many years and recently switched away, I can tell, it is not a matter of taste, some languages are simply worse, which implies that some are better. There is no "equal rights" to enforce in this domain.
[edit: clarify]
Interestingly (perhaps) I repeatedly hear from people with language/humanities background that they tried both python and perl and found perl much, much easier to start to get things done with - the more natural-language-ish aesthetic of perl being a strong contributor to that (I'm a pure maths grad but my parents are both Eng. Lit. grads, so I guess I sort of count in the "humanities background" category).
On the other hand, people with non-humanities backgrounds almost always found python easier to start to get things done with, even if they later found perl to be their preference.
Above comments based purely on anecdata; take them for what you will.
Most jazz musicians I have talked to and taken clinics from really don't like sheet music though, as it is an ineffective and inconcise way to represent a tune's structure and melody, hence why they prefer charts. Charts really are worlds ahead of sheet music in my opinion.
Of course when you start out reading notes, double-sharps are confusing as heck.
I do still think that in the end people are just conforming to the standard to make life much much more easier, and that it isn't so much that certain things are better for the expert then the novice, but that experts are more used to the standards than a novice is.
I feel it's more of a matter of personal style than a programming language x being more efficient when you become an expert when compared to language y. Some people really fly with Perl, whereas other people are more of a Python kind of person.
About the double sharp, it often has to do with tonality. Classical music is typically more tonal than jazz. The sharp is needed when you temporarily change tonality, and some tonalities just need double sharps then and there –Gsharp dur for instance. If you wrote the natural note instead, it would not convey the intended tonality.
I was also unnecessarily harsh towards double-sharps as well, when I was learning piano I would sight read a lot of easier pop/rock sheet music, and there were a few pieces I encountered with an unnecessary double-sharp that would catch me off guard because it was uncommon for the style.
I don't feel that any written music can or could adequately convey the feel, shape, or nature of the music--you've got to work through it with the group, or hear someone who already understands the piece.
A more interesting test to me would be something like seeing how fast experts in a number of languages could extend or find a bug in code by other experts. I think there’s been a little research on this, but I don’t know enough to link to the best of it.
As I said, I dislike Perl’s syntax. But I think that, on the available evidence, it makes sense to see that an an opinion on the level of disliking cilantro, not on the level of disliking geocentric cosmology.
An analogy: I don’t know how to read sheet music with any proficiency. It would be easier for me if note duration were shown by horizontal length instead of the system of tails and open/filled circles. However, this wouldn’t be as good for experts, who care more about fingering than about being able to see the melody in the most literal way.
I don’t happen to like perl’s syntax, but this study by itself isn’t proof that it’s objectively bad for the people who use it heavily.