hoxworth/json-schema — comment on commit 2ff929645217a300875b5f3e5b0aabddfbf33c1a
File:  line 0
By myronmarston:

I appreciate the desire to keep the dependencies to a minimum (it's far better than the opposite "including everything you can" philosophy), but I'm not sure that I see many advantages to pulling multi-json in like this. You still have an external dependency on either json-gem or yajl-ruby; so this isn't removing external dependencies entirely. In the app I'm working on that uses json-schema I need to use multi_json for some other stuff, and I'm concerned about potential weird, subtle problems if two versions get loaded (i.e. the gem-installed version loaded via `require "multi_json"` in the app code, and the version vendored and loaded here). Vendoring a gem so as to avoid it as an external dependency (rather than relying on rubygems doing what rubygems does best) seems like not a good idea in general to me.

That said, ultimately, it's your project, so feel free to do what you want :). I can always maintain my own fork without this.