Just trying to understand the issues/solutions for the (de-)serializing of clojure data structures…
With the tag literal support of 1.4+, is that kind of the idiomatic way of the future to structure protocols for serialized clojure data/code? When you say that Nippy is much faster than the reader, are there ways to improve on or optimize the reader? (guess the speed improvement is only achieved for true data (?)) Thanks, Frank. On Jul 7, 2012, at 11:24 PM, Peter Taoussanis wrote: > Hi Sun, > > Can't wait to test it out. > > Great- thank you! Let me know how it goes and if you run into any problems. > > By the way, do you have a performance comparison between Nippy and > carbonite(the one wraps kryo) ? > > Not yet, but plan to. I should probably also compare to JSON and a few > others. I would expect Carbonite to be faster since Kryo is faster than > standard Java serialization (which is basically what Nippy uses). > > The goal for Nippy isn't outright speed but a particular balance of speed, > simplicity, and usability that I was looking for for some of my own > applications. Actually, come to think of it, I will add links to some > alternatives like Kryo. > > -- > You received this message because you are subscribed to the Google > Groups "Clojure" group. > To post to this group, send email to clojure@googlegroups.com > Note that posts from new members are moderated - please be patient with your > first post. > To unsubscribe from this group, send email to > clojure+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/clojure?hl=en -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
