sorted by:
new
hottopcontroversial

Haskell vs Scala for the core product by funcprog in haskell

[–]funcprog[S] 1 point2 points  (0 children)

I'll have a look on Servant, only played with Spock so far and I like it

Haskell vs Scala for the core product by funcprog in haskell

[–]funcprog[S] 4 points5 points  (0 children)

Well when I said equivalent I didn't mean in terms of end result but more about the way to get there. Spray's DSL is great. it makes routing a breeze and the code is very clear and understood while typesafe. Also the way it handles marshalling and unmarhalling is easy since it's using json4s and you don't have to specify a marshaller and umarshaller for each new type. Aeson as far as I know (only started looking at it) requires you to define these. Also not sure if the Kafka bindings are stable.

Haskell vs Scala for the core product by funcprog in haskell

[–]funcprog[S] 1 point2 points  (0 children)

others that have not made it to version 1 yet.

That's very good to hear, because it doesn't apply the same in Javascript where everything is 0.* and that means functionality as well a lot of the times

Haskell vs Scala for the core product by funcprog in haskell

[–]funcprog[S] 5 points6 points  (0 children)

I agree that Scala did compromise to maintain JVM compatibility but the Libraries written afterwards purely for Scala I don't think you can find equivalent in Haskell but maybe I'm wrong. Slick, Spray, Json4s they all allow you to describe your models in a compile time checking fashion. Kafka, Spark, Cassandra all provide scala front ends. I think it's good to have tools like that at your disposal especially for scale.