dons:

jason.dusek:

...

Too bad they didn't pimp Haskell as practical.

It looked like an archaic view of Haskell based on reading wikipedia, imo. Perhaps we should take charge of the wikipedia page, if it is that influential.

To those reading, the wikipedia article is here, http://en.wikipedia.org/wiki/Haskell_(programming_language) Feel free to improve it. We have lots of good content about the current state of the language, compilers, libraries, applications, domains of use, size of community, commercial use and so on on haskell.org, so just apply what you know. Perhaps we can get a better article out of this that more accurately reflects the thousands of people reading this list and using Haskell, the thounsand or so libraries, our excellent optimizing compiler, and the broad range of apps being produced. -- Don

That "article" is an incredibly half-assed job. It reads like a high-school essay, thrown together in a hurry before a 1 hour deadline. Maybe it's a good sign that people think they have to do this, but it really doesn't help anyone who wants to know why FP might be worth learing. 2008/12/8 Stefan Monnier :

...

http://www.ddj.com/development-tools/212201710;jsessionid=3MQLTTYJRPL3CQSNDL...

Do they purposefully obfuscate names? I mean who are those "Martin Obersky" and "Don Sype"?

Stefan

_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe

-- Push the envelope. Watch it bend.

For this purpose, the only thing better is if we could somehow get them to mention Microsoft everywhere they mention Haskell. Any actual explaining would just get in the way :)

Doesn't quite work without explaining, because one would have to be very careful not to mis-represent financial support by some as endorsement by the whole; but if one were to ask those who have contributed financially to Haskell development in some form or other for their permissions, one could make quite an interesting little list (not to mention the vastly larger list of people who have contributed their time, efforts, and ideas). There have been occasional discussions of language-specific or FP-in-general industry consortiums. Perhaps the simpler form of "Haskell sponsorship" with mutual bragging rights for haskell.org and sponsor could be a seed corn for such organisations. These days, being associated with FP is no longer something that needs explaining, let alone defending, so sponsors could get something out of their contribution, such as cute little logos, tea-cups and t-shirts (apart from the prime motive of better Haskell;-). Imagine all the students that universities could attract by being a "Haskell campus", not just turning out "Haskell engineers", but "supporting Haskell development" by contributing staff time. Imagine all the competent developers and major customers companies could attract by being a "Haskell sponsor", being actively involved in "Haskell frontline development&research". Imagine all those pretty Haskell logos on all those webpages. oops, wrong universe again;-) Claus PS. Of course, if you do go down that route, your next Haskell job in industry might be representing your company on a committee to decide the internationalization of an XML-based interchange format for unicode lambda characters, with the usual sub-committees for upper-, lower-, and othercase variants, each with at least two spin-off standards representing minority preferences or implementors' we-just-did-it decisions. So be careful what you wish for.