Anyone tried to address this issue?

Which one? The proliferation of operators? Or library quality? Or libraries overlapping in intent and interface?

Haskell has two levels of "standard library" (base and Haskell Platform), and two levels of "open source third party library" (Stackage and Hackage). Between all the teams for ghc, haskell platform, stackage, and haskell.org, there's quite a lot of people that have been working generally on Haskell's library situation.

On the other hand, I don't know anybody that has been working on cutting down on operators. (lens seems quite determined to accomplish just the opposite.)

-- Dan Burton

On Tue, Dec 16, 2014 at 12:41 AM, Giacomo Tesio <giacomo@tesio.it> wrote:

2014-12-12 14:22 GMT+01:00 Johan Tibell <johan.tibell@gmail.com>:
Everything doesn't have to have an operator! We use operators a bit too much. It hurts readability of code when lines start looking like APL.

Probably this has been discussed already (and I'd like to read previous material, btw, so please give me some reference), but as a long time programmer with experience in many different paradigms and languages I too feel Haskell a bit cumbersome from this point of view.

I mean, the language in itself is the best I know, but libraries have different levels of quality and in general they miss organization: they often overlap in intent and interface, for example.

Anyone tried to address this issue? And if so, how?

I can see how backward compatibility prevents Haskell to be polished, but it's a pity.
It's like an handbrake for it's evolution and adoption!

Giacomo

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