documentcloud/underscore — comment on commit 9e4192729375c8eab68913d36de9fbb8ffbbdfcc
File:  line 0
By braddunbar:

I've been watching this issue rather closely and I'm still not sure which approach is correct. On the one hand, if my users were encountering these issues regularly I would certainly appreciate the support. On the other hand, I feel that it is a rather significant change (regardless of the byte count) and that it somewhat obscures the code in the name of issues I'm not having and don't foresee having. Underscore's implementation is rather simple and beautiful and that accessibility is a large part of what draws me to it.

@jdalton I would suggest that perhaps this is an issue that would benefit from a fork. This would allow us to gain a clearer picture of the user base that is encountering this issue and wants a fix from underscore. Furthermore, one could switch to the forked version easily if/when these problems are encountered. Certainly this would be better than dismissing the library as a whole.