News for hackers. Stuff that matters.
Re:Reflecting on Haskell in 2016 by elliotec on Monday December 26, 2016 @02:01PM (#13259321)
Not having examples in documentation is a non-starter for me. It seems like there is a superiority complex there, that the Haskell community thrives on. That's ok I guess, I've never heard a practical use for it and I'm sure it will remain in it's insular state for the foreseeable future.
Re:Reflecting on Haskell in 2016 by evincarofautumn on Monday December 26, 2016 @02:39PM (#13259464)
I strongly prefer having examples, too, but I doubt it’s due to any kind of “superiority complex” that docs are lacking. Writing good docs takes work, and some library authors are more willing to put in that work than others. Well-designed types can give you a great deal of what you’d get from docs in other languages, but they aren’t a panacea.

Now, I find it very hard to believe that you’ve never heard of a practical use for Haskell. Do you just not care about the things that companies are using it for? (Compilers, web apps, backend services, finance, educational apps…)

Re:Reflecting on Haskell in 2016 by armitron on Monday December 26, 2016 @08:01PM (#13260641)
Can you name a single, widely used (outside the Haskell camp) opensource application written in Haskell?

I can only think of "darcs" which for all intents and purposes was a failure. IIRC, one of the darcs retrospectives I've read, pointed out that GHC runtime behavior and its hard-to-foresee and hard-to-measure complexity properties, was a problem.

Moreover, another high-profile failure that springs to mind, is Joel Reymont (wagerlabs.com) trying to write a high-performance poker server in Haskell and eventually abandoning it in disgust due to non-predictable behavior of the GHC runtime. He delivered it (with assorted paeans) in Erlang instead, which proved quite lucrative for him.

I used Haskell for 2 years during my undergraduate degree, for program analysis. It was a good choice for such a theoretical domain. Some time later, I had another look at applying it to more practical problems. Besides the slight turn-off due to cultish behavior - which is also obvious in this thread, many posts excuse the lack of documentation or posit it as not a problem (!?), if not outright exalt it! - I got from the community itself, the language felt completely sterile and - most importantly - not fun. The syntax is also atrocious.

I concluded that if static typing was needed, I would pick ML every single time over Haskell. I also have no affinity with Haskell's type system (in the sense that it leads to better programs) or its interactive nature (laughable compared to Lisp/Smalltalk). I also remember something Sussman said, "Haskell is the most advanced of the obsolete languages" [1], and can't help but chuckle.

[1] https://www.infoq.com/presentations/We-Really-Dont-Know-How-...

Re:Reflecting on Haskell in 2016 by sjakobi on Monday December 26, 2016 @08:57PM (#13260799)
> Can you name a single, widely used (outside the Haskell camp) opensource application written in Haskell?

How about pandoc, PostgREST, git-annex, the Elm compiler?

You can find more examples here: https://github.com/Gabriel439/post-rfc/blob/master/sotu.md

Re:Reflecting on Haskell in 2016 by sjakobi on Monday December 26, 2016 @11:14PM (#13261239)
What's the reason for the downvotes?
Re:Reflecting on Haskell in 2016 by greenrd on Tuesday December 27, 2016 @02:14AM (#13261747)
Darcs was mostly a failure because no-one, not even the original author, could satisfactorily explain its patch model - whereas git's patch model is simple and easy to understand. That has nothing to do with Haskell.
Re:Reflecting on Haskell in 2016 by vanessa98 on Friday December 30, 2016 @12:08PM (#13285472)
Oh man, please don't ever use Joel Reymont as a language reference - his noisy, uninformed, continuous churn through various programming languages was exhausting back in the day. Just be thankful the hack has gone quiet.
Re:Reflecting on Haskell in 2016 by PopsiclePete on Tuesday December 27, 2016 @11:28AM (#13264023)
The only piece of Haskell I rely on is Pandoc. Which is awesome. But I think hardly a shining example of "Look what you can do in Haskell that you can't do in X!"
Re:Reflecting on Haskell in 2016 by codygman on Monday December 26, 2016 @09:50PM (#13260971)
Re:Reflecting on Haskell in 2016 by mjhm2539 on Monday December 26, 2016 @02:32PM (#13259439)