In a large Rails app, the number of dependencies can grow quite large. In such an app, the risk of unresolveable version conflicts between versions of a single dependency grows ever higher. As a library, it would be very helpful to consumers if the library's own dependencies were kept to a minimum. This would minimize or eliminate any such version conflicts.

Case in point, the HTTParty gem is a dependency that could be removed. From what I can tell, there are only two small use-cases for HTTP in this gem: event dispatcher and the http config manager. Neither object has that much extensive use of HTTP.

I would request that these classes just use net/http from the ruby standard library instead of pulling in a dependency.