News for hackers. Stuff that matters.
Re:Reflecting on Haskell in 2016 by 59nadir on Monday December 26, 2016 @04:56AM (#13257684)
Elm was written off because it still does an incredibly bad job at implementing polymorphism. It has a hardcoded "Show" class for turning things into strings and only certain privileged entities can be turned into strings using it.

It's all in all a very bad way to do polymorphism and that's what the article points out. It's especially odd in a language like Elm, that obviously is supposed to be like other ML-like languages.

Re:Reflecting on Haskell in 2016 by zoul on Monday December 26, 2016 @05:34AM (#13257770)
My point is: I tried several times to write something in Haskell, I really want to like the language. But each time I felt too stupid for it, it just feels like too much work. In Elm I got a working app in a day and enjoyed the experience. Isn’t there a lesson for the Haskell community other than “Elm does polymorphism wrong, meh”?
Re:Reflecting on Haskell in 2016 by eklavya on Monday December 26, 2016 @09:19AM (#13258303)
Maybe both are catering to different programmers?
Re:Reflecting on Haskell in 2016 by 8fGTBjZxBcHq on Monday December 26, 2016 @01:35PM (#13259232)
Is Haskell catering to programmers who don't want to be able to get a simple app up in a day? Who are these programmers who fight through the first steps of picking up a language and are thrilled by that.
Re:Reflecting on Haskell in 2016 by eklavya on Tuesday December 27, 2016 @04:22AM (#13262168)
Maybe yes, You can not learn Haskell in one day, if that was your point. My point is learning Haskell takes time and it's hard and it is totally understandable if for some people that is not a good investment.