Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSYNC #49

Closed
trans opened this issue Dec 1, 2012 · 6 comments
Closed

JSYNC #49

trans opened this issue Dec 1, 2012 · 6 comments

Comments

@trans
Copy link

trans commented Dec 1, 2012

I notice Oj has a serialization format, Object JSON. That's cool. But what I'd really like to see is support for JSYNC (http://jsync.org/).

@ohler55
Copy link
Owner

ohler55 commented Dec 1, 2012

JSYNC does not seem to be very active. It claims to be under heavy construction and that was 2 years ago. Have you seen any evidence that it is being used?

@trans
Copy link
Author

trans commented Dec 1, 2012

JSYNC was created by Ingy döt Net one of three main YAML designers. As such it is well thought out, mapping YAML concepts back to JSON. Problem is (AFAIK) no one has implemented it yet. Which is why it would be so great, if someone finally did.

@ohler55
Copy link
Owner

ohler55 commented Dec 2, 2012

I can understand your desire for JSYNC to gain traction but implementing it as part of the Oj gem does not really make sense at this point in time. The usual path to get JSYNC more widely accepted would be to write a JSYNC parser using the Oj gem and when the edge cases are worked out and a spec finalized I could look at making Oj parse the JSYNC spec. Without a stable spec I would just be chasing my tail trying to keep up with changes in JSYNC as issues were discovered and worked out.

Would you be interested in writing the first JSYNC parser making use of the Oj gem?

@ohler55
Copy link
Owner

ohler55 commented Dec 9, 2012

No reply. Closing this as an issue.

@ohler55 ohler55 closed this as completed Dec 9, 2012
@trans
Copy link
Author

trans commented Dec 9, 2012

Sorry. I'm just very busy. I think I can put together a parser --as least I don't think there should be anything too difficult about that. It's more the emitter that I think will be difficult.

Anyhow, I'll give it a good as soon as I have some cycles to spare it.

@ohler55
Copy link
Owner

ohler55 commented Dec 9, 2012

When you get going let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants