----- Original Message ----- > spray-json only relies on parboiled, a library mantained by the spray-team > itself. Right now it's performance is much worse than lift-json ( > http://engineering.ooyala.com/blog/comparing-scala-json-libraries) but that > would change when they finished parboiled2.
Thanks for this feedback, Luis! > And alternative could be argonaut.io but you would bring scalaz as a > dependency. Yes, I thought about mentioning Argonaut, but was concerned about bringing in scalaz as an immediate dependency. (From a packaging perspective, Argonaut is equivalent to Lift in this regard, since IIRC scalaz is a build and runtime dependency for lift-json.) More generally, though, I wasn't sure how well the Argonaut style would fit in to Spark as a replacement for lift-json. If it's not a concern to bring in scalaz or that style of code, then Argonaut is worth considering as well. (It looks like json4s and jackson-module-scala are excellent candidates in any case.) best, wb
