Conrad Zimmerman

I currently don't see any good reason to copy prototype properties. I know underscore.js does this, but it seems that copying prototype properties could make it easier for bad programming...

OK, never thought about inherited config properties. I guess that could be a valid use case for this behavior. I would agree on adding a note to the docs. As...

I wouldn't be opposed to `mlib`. `mutils` to me sounds like a better name, since it can be pronounced one word (e.g. mootils), but might be too close to mootools....

`stdlib.js` is available both on github and NPM. It's kinda redundant to have the `.js` on NPM, but it would make the package easier to find by googling. I think...

I would be OK with that. Like the sugar analogy :smiley:. Would the current `amd-utils` become just `mout`, or would it be `mout-std`?

Underscore.JS [`_.clone`](http://underscorejs.org/#clone) function _does_ copy properties on the prototype, but _does not_ actually use the original prototype. I don't think that this is necessarily the best behavior, but some people...