> There's more to it than that. See "Why does Pivot include its own collection > classes?" in the FAQ: > > http://cwiki.apache.org/PIVOT/frequently-asked-questions-faq.html > > Honestly, I'm getting a little sick of having to justify why we wrote our > own collections. They are an integral part of the platform and we want the > most optimized implementation we can get. The JDK collections just don't cut > it for our use cases. I don't hear anyone complaining that the Groovy and > Scala guys, for example, defined their own collections (presumably for > similar reasons). Why is it such a big deal for Pivot to do so? >
Because Groovy and Scala are new languages. Pivot is not. I think you're misconstruing the argument. I __like__ Pivot's collection classes. They are part of what makes it special. What I __am__ arguing against is effectively inlining java.util.HashMap into pivot.util.Map. I just can't see that there is any performance or functionality gain to be had from doing so. Debugging is really not any harder, especially if toString() is done properly. And you're adding to the maintenance burden. Is there some specific Pivot thing that you believe a custom implementation can take advantage of? Regards, Noel.
