jrburke/backbone — comment on commit 57c2029117649452c6cf4d3337e03f5d52bb8331
File: backbone.js line 27
By jrburke:

[This amd-implement thread](https://groups.google.com/group/amd-implement/browse_thread/thread/8a1e39248ccd0f32) talks about this kind of boilerplate, and John is aware of the issue for curl. Feel free to comment on that thread if you have concerns about the general approach, as this kind of boilerplate will be suggested to other libraries.

The toString concern with PS3 are overcome by doing a build with an optimizer. Since the primary use case for non-built AMD files is debugging and the debugging story on those browsers is awful and those devices should have a built code anyway, developers using AMD code on those devices should be working with built resources.

The tradeoff is: amount of boilerplate junk vs. catering to very small edge case. I believe having smaller boilerplate that is easier for people to adopt is worth it given the build mitigation for the very small edge case. This was the reasoning for allowing toString scanning in the AMD API.