Hopefully this will work its way through the correct channels to a MySpace developer who can address this question...

Why does myspace-ruby-0.7.1 require "json/pure" instead of just "json"?

The docs say: You can install json via rubygem, which should provide a native C 'ext' and pure ruby 'pure' extension. The native 'json/ext' module is faster, but could lead to some compatibility issues, so we stuck with the pure variant.

Can you elaborate on "compatibility issues"? Is this a mswin32 bug only (and if we're operating in a *NIX environment, we can safely use the C extension "json")? Are there specific edge cases you can highlight?

 Yes, this is a win32 specific bug we hit on a couple occasions, which was related to a couple installs that had built win32 ruby from source.   We should probably just switch back to native json/ext or check the installed json libs on install to see what to do.  I'll add it to the TODO.

 And yes, if you're non-win32, you can just use native json.

 

 

 

 

Awesome! Thanks for the quick response.