| qcr | easyjson | |
|---|---|---|
| 1 | 10 | |
| 1 | 4,350 | |
| - | 0.8% | |
| 0.0 | 2.3 | |
| almost 2 years ago | 10 days ago | |
| Go | ||
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
qcr
-
What type of software do you write at your workplace?
I created Turandot, Candice, Reposure, Knap, CNCK, QCR, multusctl, and a whole bunch of dependent libraries, and also participate in a bunch of other K8s-related projects.
easyjson
-
Google's Go may add telemetry reporting that's on by default
Compile time means you catch issues at... well compile time. It also means that the code is optimized. You can look at the performance different between encoding/json and easyjson for why you may desire that.
- JSON encoder/decoder supporting omitempty on structs
- TinyGo Reflection?
-
Wasm difficulties in Rust, Haskell, and Go
easyjson produced an empty file
-
Using a json lib other than encoding/json
There is https://github.com/mailru/easyjson out there if you are absolutely sure that serialization is the bottleneck. Otherwise I'd go for stdlib.
-
What type of software do you write at your workplace?
https://github.com/mailru/easyjson fast JSON (de)serializer which go generates code instead of using reflect at runtime.
-
Whats the fastest JSON unmarshaling package as of right now?
If you know the schema of the JSON ahead of time and you need to parse the whole object, I would recommend https://github.com/mailru/easyjson as that will likely give you the fastest result. This works in almost all use cases, and easy to use features such as string interning can save you a lot of time on memory allocation if you parse a lot of JSON objects with identical values.
-
Some Go(lang) tips
What to use Easyjson is about the top of the pack and it's straightforward. The downside of efficient tools is that they use code generation to create the code required to turn your structs into json to minimise allocations. This is a manual build step which is annoying. Interestingly json-iterator also uses reflection but it's significantly faster. I suspect black magic.
-
Is there a JSON parsing library that generates specialized code for types?
I'm looking for something similar to https://github.com/mailru/easyjson where one can generate a concrete JSON parser for some types.
-
Обережно кодогенерація
Бібліотека easyjson теж для серіалізації працює через додатковий код замість використання рефлексії. Але після внесення в easyjson одної з оптимізацій, час від часу почали отримувати зламаний JSON, ось приклад тесту який покаже помилку.
What are some alternatives?
ozzo-validation - An idiomatic Go (golang) validation package. Supports configurable and extensible validation rules (validators) using normal language constructs instead of error-prone struct tags.
fastjson - Fast JSON parser and validator for Go. No custom structs, no code generation, no reflection
goleveldb - LevelDB key/value database in Go.
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
go-json - Fast JSON encoder/decoder compatible with encoding/json for Go
gogoprotobuf - [Deprecated] Protocol Buffers for Go with Gadgets
simdjson-go - Golang port of simdjson: parsing gigabytes of JSON per second
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
go-warning-codegeneration
jsonparser - One of the fastest alternative JSON parser for Go that does not require schema
zerolog - Zero Allocation JSON Logger
compress - Optimized Go Compression Packages