Re: Standard Haskell

[Chris Burdorf]

Please pardon me if I come across as a smug outsider, but it seems
like a Catch-22 situation:

  1. Designers would like more people to program in Haskell.
  2. The industry prefers to use standards.
  3. Designers realize that a standard will more or less put them out
     of business.


This is why we are stuck with C++ these days, because, for
example,  the Lisp community
couldn't really settle on a standard (eg. Standard Lisp, Common Lisp,
ISO Lisp, EuLisp, Scheme, ...).    AS a result, the gap between
what researchers know about programming languages and what us poor
slobs in industry use continues to widen.   Java may take over, but
not because it's a wonderfully elegant language.

(These are my own opinions and not those of my employer)