Maddy 0.3.0, a functional object operations library
kitcambridge.github.com
kitcambridge.github.com
I use _.map and co with objects all the time. It works fine. I don't see how it is any different from Maddy.map. What did I miss?
Also, if the major difference is bugfixes in iteration, why don't you just contribute to underscore?
Secondly, Maddy implements other features apart from iterator functions, including deep equality and object serialization. These methods operate on cyclic structures, which I've yet to see fully supported in any other functional JavaScript library. I've contributed a patch to Underscore that adds support for cyclic structures to its `_.isEqual` method, but it's still in review, and will likely remain so for some time.
Finally, while Maddy was philosophically inspired by Underscore, it isn't intended to replace or challenge it. You're free to continue using it as you prefer; I'm not suggesting that you replace Underscore with Maddy in your code. They are different libraries with different target audiences: Underscore is a general-purpose utility library, Maddy is a niche object operations library. In sum, it's simply another option for those wanting a more conventional functional programming library to work with objects.
I'm clearly too noob to understand the "that the use of objects as hashes in JavaScript was inherently broken". I understand you disagree with this conclusion? Is there any URL to the discussion that I can read? And why do you disagree?
What's up with all these aliases? Isn't one name enough?