History of Haskell
1 The History of Haskell
"A History of Haskell: being lazy with class", Paul Hudak (Yale University), John Hughes (Chalmers University), Simon Peyton Jones (Microsoft Research), Philip Wadler (Edinburgh University), The Third ACM SIGPLAN History of Programming Languages Conference (HOPL-III) San Diego, California, June 9-10, 2007.
This paper describes the history of Haskell, including its genesis and principles, technical contributions, implementations and tools, and applications and impact.
2 Giving feedback
When we publish the final version, we'd like your feedback, because we can still make small changes. You can do so in two ways:
- Send us email personally (email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org)
- Add comments to the Version 2 "Talk" page.
So you can remember what you wrote before
- Here is the Version 1 "Talk" page. I have added notes to it saying what I think I've done, with a few still remaining. Any concrete help with the remaining ToDos would be gratefully received!
If you like, you can instead send email to the Haskell Cafe mailing list, but we are less likely to follow that closely.
3 Things to think about
Writing a paper like this is a big task, and one that is very different to the sort of research papers that we usually write. So we would really appreciate your help in making it better. Here are something thoughts and questions that we invite you to bear in mind as you read it:
- We experienced a tremendous tension between
- On the one hand, comprehensiveness and doing justice to all those who have contributed to Haskell
- On the other, keeping the paper "alive". We don't want it to become a boring catalogue of everything that has ever happened to Haskell.
- Please don't feel slighted if we have not mentioned your own fantastic work. Instead, politely correct us. And bear in mind that the above tension means that we just can't include everything.
- We are interested in feedback at all levels: accuracy, coverage, structure, tone, fairness, level of detail; as well as spelling and grammar. Of these, spelling and grammar are the least important!
- The applications section is particularly patchy. One possibility would be to include a much longer list of applications and application libraries, but given in much less detail. Please send us suggestions: the name of the application, who wrote it, roughly how big it is, and (where posssible) a citation of some kind that gives more detail.