scalaz

A lot of Scalaz and Shapeless duplicates things that were implemented less well in the standard library.

Standard-library futures aren't completely controlled (and overuse implicits) so there is scalaz-concurrent Future which is almost but not quite the same.

For those who don't understand: Scalaz is an additional layer of syntax and tricks on top of what is already there.

Interesting that they were working on a scalaz course and book in 2011.

The top comment was from a Python guy who said that this is exactly what he is missing from Scala, but the other answers were in the form of - just use scalaz / scalaz steams.

While I have received some helpful advice from Tony Morris on the Scalaz mailing list, I think that attitudes like his are poisonous.

It measures the performance difference between scalaz.

:) You (and the article) are right: scalaz's Task can minimize context-switching overhead.

Good Scala - FPish Scala, coupled with Scala libraries such as Spark, mllib, scalaz, Scalding, Apache Math, colt, akka.

There are certainly those that use it anywhere between Haskell-like with scalaz to Java-like only without having to write constructors and getters (in fact, Spark is written, I believe, closer in the latter style).

It's split into two, the people who wish Scala is Haskell (shapeless, scalaz &c) and the people who want Scala to be Enterprise Quality™ It causes lots of issues, as their goals for the language are completely different and Scala devs are usually in one camp or another.

Let me add that we have an awesome, FP strong team and architecture, if you are looking to apply things like scalaz, shapeless and monocle in practice and have fun discussions about where to best use concepts like Monoids, how to best organize data flow, etc, that's happening here.

In scala the idiomatic way to do "short-circuit the rest of this in some cases" is usually for/yield with a type like scalaz's \/.

The oldest guys at my company are the ones teaching the classes about Haskell or Scalaz.

Oh yes I forgot the memory hog of IntelliJ, especially with Scalaz, and if multiple projects/windows openend at once...

Scalaz has a typeclass for mappable things and it's called Functor.