I would agree that there are probably more "Haskellish" compile-to-JS languages, but the wiki mentioned CoffeeScript and TypeScript. Surely Elm ranks above them in your book?
Besides, Fay doesn't have typeclasses, either, and it's mentioned.
I wasn't making the claim that Elm was somehow better than those options, just that I was surprised it wasn't included. I've just played around with Elm, nothing serious.
You're correct that Elm seems more like a DSL in some ways with its required FRP, and I agree that typeclasses and HKTs are nice, but if I could choose between doing my day job in Elm or staying with JavaScript, I know which I'd pick (hint: it's not JS).
Re:The JavaScript Problem
by coolsunglasses on Sunday April 27, 2014 @02:38AM
(#7654195)
Do not underestimate how powerful and useful HKTs and typeclasses are until you've used them in anger.
I have a guide to learning Haskell here: https://gist.github.com/bitemyapp/8739525
You should give it a whirl.
Just use PureScript if you're fortunate enough to know alternatives to JS exist :)
PureScript is a better choice for a Haskell'ish language that is generically applicable to both browser and node-backed JS.
Importantly, you can decide how you want to do FRP/callbacks/whatevers according to the needs of the libraries/app/problem you're working with.
Also, PureScript has typeclasses, higher kinded polymorphism, the works. It even has some cool stuff that Haskell does not built in!
See this post for example of why higher-kinded polymorphism is important: http://bitemyapp.com/posts/2014-04-11-aeson-and-user-created...