Greg Hazel wrote:
I'm interested in a JSONgem version of encode as well. I ran in to this
which was only recently fixed. I would rather use the json gem than wait
for Rails to find all the bugs and improve the speed of the home-grown
I circumvented the Rails hack by making a hack of my own.
Hopefully, the Rails core team does not create more hacks of this
nature. Better yet, the hack should be removed. I want to choose which
version of to_json I use (instead of some Rails core dude).