Because Groovy and Scala are new languages. Pivot is not.
See my earlier response to Martijn - while Pivot itself is not a language, WTKX arguably is. So I think the comparison is valid.
I think you're misconstruing the argument. I __like__ Pivot's collection classes. They are part of what makes it special.
I am glad to hear that.
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.
Pivot maps and JDK maps are not equal. The fundamental operations are the same, but Pivot maps fire events, perform auto-sorting, and iterate differently. These features cannot be as efficiently implemented using JDK collections as they can natively.
Debugging is really not any harder, especially if toString() is done properly.
When stepping through code, it is often easier to browse the contents of a data structure than rely on console output. Use Eclipse to view the contents of a Pivot ArrayList vs. a ListAdapter and you'll see what I mean.
