This code badly needs a piece of documentation outlining:<p>* how it differs from Google Guava Collections,<p>* what are the tradeoffs and performance/memory characteristics of the collection types.<p>I couldn't find an answer to the question "why would I use this?" — and I am actually looking for collections with certain properties (for Clojure, but it doesn't matter much in my case).
I have no idea whether this code is any good or not (I'm a PM by trade) but in Investment Banking, GS has very much a "build rather than buy" mentality, and I get the impression that techies are treated with more respect than some places.<p>I have heard from people that have worked there, that one of their main sources of competitive advantage is their bespoke settlements system, Sec DB. Apparently, it models every instrument as an object, and adding new derivatives and instruments is relatively straightforward.<p>A bunch of senior managers from GS took over the tech organisation of a different bank I was involved with, and one of the first things they did was to start creating a new settlements and trading system, even down to the level of creating their own RDBMS as existing ones didn't do what they wanted.<p>In most banks, you could get laughed out of the office if you said you needed to write a new RDBMS from scratch.
109 days later, a PR move regarding the german documentary about the bank? (cf. <a href="http://www.huffingtonpost.com/vivian-norris-de-montaigu/the-omerta-surrounding-go_b_1852253.html" rel="nofollow">http://www.huffingtonpost.com/vivian-norris-de-montaigu/the-...</a>)
"Provides replacements for ArrayList, HashSet, and HashMap optimized for performance and memory usage."<p>Sounds interesting, would like to know a bit more. Looks like I have to find out for myself if I want answers