Hacker News new | ask | show | jobs
by tung 5491 days ago
Digging around, I found that the author used the JSON gem, relying on to_json taking an optional generator arg. But, yajl-ruby and ActiveSupport define to_json themselves without that, leading to breakage. Those, and the fix for his project[1], are all on GitHub.

The author claims most Ruby programmers are monkey-patching and causing these problems. That's almost right: they were. But by and large, they know better now, and would happily replace it with better code, if they could just find it and fix it: that's the real problem.

The author could help by, say, logging an issue, or forking and pull requesting a fix. I checked GitHub; his ID, bcoe, doesn't show in the issues, nor in the pull requests of yajl-ruby's GitHub page[2].

I'm not saying he must do this for every problem with every open-source project he happens across, but even one contribution helps more than this steam-venting blog post.

[1] https://github.com/bcoe/tire/commit/2dd5fc03

[2] https://github.com/brianmario/yajl-ruby