Actually, unless I'm misunderstanding you, there is no maintenance issue. JSON has no version; it simply is. There will not be a JSON 2.

With that constraint, you should be confident that any porting activity you do should be stable for a long time to come.

On 31-Oct-06, at 8:14 PM, Carl Shimer wrote:

Rewriting this stuff isn't hard but is more of a maintenance issue.  anyway it looks like it easier to simply rewrite the code that breaks because of json.js with the addition of writing nastygrams to tell other devs how to do proper JS iteration :)


me Pete Forde: Partner at Unspace Interactive
contact | [EMAIL PROTECTED] - 416.548.8444


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs
-~----------~----~----~----~------~----~------~--~---

Reply via email to