Linked by Eugenia Loli-Queru on Wed 1st Nov 2006 02:49 UTC
"The article is about my experience with Haskell and the process of working with it. I will describe which features of Haskell I used to implement particular aspects of my interpreter, how they're different from the object oriented world, why they helped me get things done faster, and how I had to change my program whenever my initial efforts took me to a dead end. While the jury's still out how well Haskell performs in other domains (I'm just starting my web application project) I hope this article sparks your interest in this beautiful language and explains some things programmers new to Haskell often find confusing." More here.
Thread beginning with comment 178049
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Member since:
2005-07-08
I see that most of the discussion so far has centered around the history and construction perspective..
by that count, even ruby and python must be in teh fray!!
how would it be from a different perspective?
Forget about how a language is implemented, or what history it has gone through.
Assume Lisp , Haskell and Small Talk are brand new languages . How can we classify those languages based only on what can we do with those languages and what we cannot? Why is one better over other for a particular problem type ?
-Ram