STOP SOPA ☣ STOP RWA
Two bills are making their way through the U.S. Congress that would have highly negative consequences for AcaWiki and the public good. Please take action against both.
Many large sites are blacked out January 18 to spur action against SOPA. Visit americancensorship.org to take action against this bill, which is a censorship and security risk for the entire internet. Wikimedia's General Counsel explains how SOPA would hurt wikis.
RWA would prohibit federal agencies from conditioning their grants to require that articles reporting on publicly funded research be made accessible to the public online. This is unjust and would specifically harm AcaWiki by greatly reducing the number of people with access to important literature — access is required to summarize. Please tell congresspeople to oppose RWA.
See AcaWiki:SOPA-RWA for planning and discussion of this message.
A History of Haskell: Being Lazy With Class
From AcaWiki
Citation: Paul Hudak, John Hughes, Simon Peyton Jones, Philip Wadler (2007/04/16) A History of Haskell: Being Lazy With Class. The Third ACM SIGPLAN History of Programming Languages Conference (RSS)
Download: https://research.microsoft.com/en-us/um/people/simonpj/papers/history-of-haskell/history.pdf
Tagged: Computer Science (RSS) Haskell (RSS), functional programming (RSS), history of programming (RSS)
Summary:
Authors describe context of Haskell's creation (many lazy purely functional research languages, desire for common language in genre), key branching factors (e.g., decision of Miranda developers to not allow their language to be base of common language; adoption of still new features of typeclasses and monads), and a number of the design decisions made, and tools, implementations, and applications now available.
Theoretical and practical relevance:
Haskell seems to have had inauspicious beginnings for a widely used general purpose programming language -- design by committee of academics, but through some combination of purity (authors argue decision to be lazy made it easier to stay purely functional), openness (of the design process, specification, libraries, and language implementations), and luck, the language seems to have remained interesting for researchers and become practical for industry, and has also influenced feature development in many other languages.
