Skip to content

Poor choice of default json provider #252

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

Open
fabienrenaud opened this issue Aug 1, 2016 · 1 comment
Open

Poor choice of default json provider #252

fabienrenaud opened this issue Aug 1, 2016 · 1 comment
Labels

Comments

@fabienrenaud
Copy link

Why choosing a default Json provider that doesn't perform so well?
https://github.com/fabienrenaud/java-json-benchmark

Jackson will go twice as fast and jackson-core is only 250kb (jsonsmart is half of that but it's also twice slower).

Most devs aren't going to pay attention to that detail and just trust what you define as default so it's better to make the better choice for them imo :)

@LowBudgetMan
Copy link

It could be worth revisiting this. It looks like json-smart-v2 no longer has a maintainer.

netplex/json-smart-v2#36

mkr added a commit to mkr/JsonPath that referenced this issue Apr 13, 2023
…lso related to json-path#682, json-path#676, json-path#513, json-path#252)

* Replace hard-coded json-smart parser with one retrieved from context (where available) or default configuration.
* This enables a project to _exclude_ the transitive json-smart dependency when setting an alternative default configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants