Well then I guess this _ has a bug because it doesn't have a 'noConflict' method. :) But to be perfectly fair, you are 100% correct: this is not a technical co

Well then I guess this _ has a bug because it doesn't have a 'noConflict' method. :) But to be perfectly fair, you are 100% correct: this is not a technical complaint and perhaps this entire sub-thread is, as has been claimed, "bike-shedding." Since this lib is designed to be loaded via an AMD-style mechanism, users can call it whatever they want, so _ is just as valid an identifier as any other. Except the obvious issue that readers of the code, examples, and any code that follows suit, will end up with this completely pointless ambiguity because _ is ultimately a meaningless name if it evolves to mean simply "some library I loaded." You may as well write sample code like: var $ = require('http'); $.createServer(...); I would think people would call that out as ridiculous and confusing.