"We provided them with a copy of P1 without explaining that it was a program, and based on preconceptions from their past experience, they had studied P1 under the assumption that it was a mixture of requirements speciﬁcation and top level design. They were convinced it was incomplete because it did not address issues such as data structure design and execution order.”
"The other kind of response had more to do with the 'cleverness' of the solution...[one of them] described the Haskell prototype as being 'too cute for its own good'.
These both sound like they could have been written today.
Reminds me of this from the Incomplete and Mostly Wrong History of Programming Languages:
Haskell gets some resistance due to the complexity of using monads to control side effects. Wadler tries to appease critics by explaining that 'a monad is a monoid in the category of endofunctors, what's the problem?'
This paper compared several properties of 80 implementations of a set of requirements. It compared properties such as run time, memory consumption, source text length, time expended developing the solution, comment density, reliability and program structure.
Overall, even though there are some obvious threats to validity, I find this work quite read-worthy.
* What is the Impact of Static Type Systems on Programming Time? (http://ecs.victoria.ac.nz/foswiki/pub/Events/PLATEAU/2009Pro...)
* Heuristic Evaluation of Programming Language Features: Two Parallel Programming Case Studies (http://ecs.victoria.ac.nz/foswiki/pub/Events/PLATEAU/Program...)
* Do Programming Languages Affect Productivity? A Case Study Using Data from Open Source Projects (http://sequoia.cs.byu.edu/lab/files/pubs/Delorey2007a.pdf)
They are all (mostly) recent papers, at least post-2005.
Furthermore, the Plateau international workshop might have some more material of interest: https://sites.google.com/site/workshopplateau/
ps: this Thursday/Friday in Delft (NL - Europe) there will be a conference related on the subject of programming languages, it's free and might interest someone: http://eelcovisser.org/wiki/future-of-programming
EDIT: fixed second link
And yeah, I agree that some studies are a bit biased (it's hard to find objective studies with a proper applied method). I just wanted to share some findings that might have been interesting to the reader and let him/her take home his/her own considerations on the matter. Entirely agree with you though.
>No-such-method exceptions mainly occur because of
null-pointer exceptions (which occur in typed
programming languages as well)
Null is a solved problem. Completely and totally solved. The fact that he didn't know this is pretty amazing.
If the topic is other experiments like this one, then I don't know. I think the idea is fundamentally flawed. There are just too many variables involved. A good litmus test is to ask yourself if you'd be able to independently reproduce the results of the experiment.
EDIT: I stand corrected; there is a Haskell job listed at the moment: http://www.indeed.com/q-Haskell-jobs.html
Have fun in Reston, VA!
I didn't mean to imply that Haskell's specialty lies anywhere near the ivory tower, either. It seems to me closer to a replacement for Ada in writing provable-yet-optimized software.