Clutch was mentioned a couple of times, so I figured I'd chime in. :-) As for why clutch uses c.c.json — I don't think there's any particular reason. Tunde chose it before I got involved, but I'm sure I probably would have done the same thing, mostly because JSON en/decoding speed isn't top-most on the performance priority list when you're IO-bound. Also, all things being equal, it's reasonable to use the 'blessed' library (an interesting topic/concept in and of itself). In any case, we'll probably be looking around at other options as we eliminate our last usages of classic contrib. (FYI, Clutch is 1.3-compatible even though it uses classic contrib.)
Dave: I'm not sure if you were referring to me, but I have been working on supporting ClojureScript views in Clutch (which are working nicely now; blog post coming shortly). *Porting* Clutch to ClojureScript doesn't make a lot of sense to me, but that could easily just be me. (It's mostly interop, so it's not really a porting task, and I'm not too keen on clients touching my CouchDB instances directly in any case.) Cheers, - Chas On Oct 6, 2011, at 6:30 PM, Dave Sann wrote: > In my opinion, the situation is not clear cut: > I might want a slower but more portable library if porting clutch to > clojurescript. > (I read that someone has this working...) > I might just want a lib that works if moving to .net in the short term but > optimise with a faster library later. > Or, I might want a fast JVM specific library > > Json parsing and writing has a relatively simple API/interface so different > implementations of the "same api" are not unexpected. > > So I have two thoughts: > > 1. Assuming a standard API. How can you practically choose between different > implementations that trade off different characteristics depending on your > need. For example: performance vs portability; or performance on certain > problem types vs others. > > 2. How many libraries might have a standard API with different > implementations. (is it worth expending time to address this?) > > In general, this is a potentially tricky question in respect of dependency > management. > > Cheers > > Dave > > > -- > 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
