fast-json VS ham-fisted

There are many more things there but you can read the README for more information. There is timing information at the bottom of the README and the fast-json project includes a comparison. My hope is that ham-fisted becomes a platform to try out ideas and build faster datastructures and algorithms that follow in the typeless functional pathway so we can carefully and measurably improve the platform we all are standing on. So please take it, try some things out, and let me know how it goes :-).

3 - Similar to 2, the savings of mutably building the collection have to outweigh the cost of persisting it. Or if you are using the transient as a mutable container (e.g. held by an item) for limited random access and writes (as opposed to say a mutable arraylist or hashmap or hashset), performance should still be substantially better for writes over the persistent counterparts. The most gains come from building up large collections, using transients to mutably collect values and then persist at the end. Similar idea (but more general) in ham-fisted.

I have taken the time in between caring for my young son to write a new library that provides higher performance datastructures and algorithms for Clojure.