>>850
no way. Haskell is pointless wankery and unreadable as shit. The community actually prefers unreadable code and reacts to readable code like some pleb rookie programmer has tracked mud through their house. Haskell's also pointless wankery of a language, with anti-features like laziness and basically being embraced-and-extended by GHC, invaliding the standard.
The worse part of course is the semantics. To even say what's going on in a typical Haskell program, even one as short as a londonize, is (inevitably) to handwave over the details, because they're fucking appalling.
Now contrast all that with the beautiful, practical, efficient, easy to follow simplicity of the J
1. take the argument, slap on a row of blanks, then rotate the array and then ravel it into a list. print that out
2. drop the first element of the argument and then echo each element separately
here's the intermediate steps (with underbars instead of blanks so it's more obvious):
'AWAKEN' ,: '_'
AWAKEN
______
|:'AWAKEN' ,: '_'
A_
W_
A_
K_
E_
N_
,|:'AWAKEN' ,: '_'
A_W_A_K_E_N_
}. 'AWAKEN'
WAKEN
see?
even a child could follow these transformations.
meanwhile with Haskell you're saying "so this constructs a lazily evaluated infinite list but don't worry in practice we'll only evaluate this portion of it and then these incredibly complex optimizations make this not insane and then if we use lenses then this 8000-line error message that summons Nyarlathotep which was our actual goal because she's cute and anime these days."