Skip to content

Fix typo #2

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

Merged
buger merged 1 commit into from
Mar 21, 2016
Merged

Fix typo #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ It does not require you to know the structure of the payload (eg. create structs
## Rationale
Originally I made this for a project that relies on a lot of 3rd party APIs that can be unpredictable and complex.
I love simplicity and prefer to avoid external dependecies. `encoding/json` requires you to know exactly your data structures, or if you prefer to use `map[string]interface{}` instead, it will be very slow and hard to manage.
I investigated what's on the market and found that most of libraries are just wrappers around `encoding/json`, the only package that had its own parser is `ffjson` (and it is awesome), but it still requires you to create data structures.
I investigated what's on the market and found that most libraries are just wrappers around `encoding/json`, the only package that had its own parser is `ffjson` (and it is awesome), but it still requires you to create data structures.
Let's be honest, JSON is not the hardest format to parse, so i wrote one that focuses on simplicity and performance.

## Example
Expand Down