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.

Sign up for GitHub

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

Jump to bottom

Question: Should we keep using GSON or move to Jackson? #2

Open
jasnell opened this issue Apr 16, 2014 · 0 comments
Open

Question: Should we keep using GSON or move to Jackson? #2

jasnell opened this issue Apr 16, 2014 · 0 comments
Assignees
@jasnell
Labels
question

Comments

@jasnell
Copy link
Contributor

jasnell commented Apr 16, 2014

The code currently uses the GSON library for all JSON stuff. Jackson, however, is generally more popular and broadly used. Should we migrate to Jackson? Doing so is a fairly large piece of work given that Jackson's custom serializer framework is much more complicated and there is a fair amount of custom serialization required. For now, GSON just works.
@jasnell jasnell self-assigned this Apr 16, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jasnell jasnell

Labels
question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jasnell