kill multi_json Dependencies

[u2]

http://www.mikeperham.com/2016/02/09/kill-your-dependencies/

Some software engineering rules:

No code runs faster than no code.
No code has fewer bugs than no code.
No code uses less memory than no code.
No code is easier to understand than no code.
Kill those dependencies. Your gems and apps will be better for it.

[rngtng]

epic thx 👍 ;)

[dblock]

Same questions and issues around merging this as in ruby-grape/grape#1274. Lets have a discussion there first?

[LeFnord]

@u2 … please can you rebase it

[dblock]

This is a non trivial change even though it looks trivial, it will impact a bunch of people in production who use gems like oj (significantly degraded performance), silently, so there be dragons!

[LeFnord]

saw the referenced discussion … though there was a decision
and it seems, that @u2 removed its fork -> so should it be closed?

[dblock]

I stand by everything I said in the Grape issue: I'd love this, but with a way to reinstate backward compatibility for existing users. A change that just drops multi_json in favor of JSON prevents that.

[LeFnord]

though this ruby-grape/grape#1274 (comment) was the decision, but yeah, it seems, nothings was done in this direction, so both PRs should be closed

[dblock]

Related, ruby-grape/grape#1623.