go-json
pflag
go-json | pflag | |
---|---|---|
24 | 13 | |
2,788 | 2,312 | |
- | - | |
3.2 | 0.0 | |
13 days ago | 14 days ago | |
Go | Go | |
MIT License | BSD 3-clause "New" or "Revised" 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.
go-json
-
API: Go, .NET, Rust
For go -> you can actually get away with the standard json encoding package. Or if you want a slightly better one, I prefer goccy/go-json
-
Rob Pike: Gobs of data (2011)
Someone made a benchmark of serialization libraries in go [1], and I was surprised to see gobs is one of the slowest ones, specially for decoding. I suspect part of the reason is that the API doesn't not allow reusing decoders [2]. From my explorations it seems like both JSON [3], message-pack [4] and CBOR [5] are better alternatives.
By the way, in Go there are a like a million JSON encoders because a lot of things in the std library are not really coded for maximum performance but more for easy of usage, it seems. Perhaps this is the right balance for certain things (ex: the http library, see [6]).
There are also a bunch of libraries that allow you to modify a JSON file "in place", without having to fully deserialize into structs (ex: GJSON/SJSON [7] [8]). This sounds very convenient and more efficient that fully de/serializing if we just need to change the data a little.
--
1: https://github.com/alecthomas/go_serialization_benchmarks
2: https://github.com/golang/go/issues/29766#issuecomment-45492...
--
3: https://github.com/goccy/go-json
4: https://github.com/vmihailenco/msgpack
5: https://github.com/fxamacker/cbor
--
6: https://github.com/valyala/fasthttp#faq
--
7: https://github.com/tidwall/gjson
8: https://github.com/tidwall/sjson
-
Data storage speed comparisons?
Drop-in replacement for the stdlib JSON package: https://github.com/goccy/go-json
-
Go is 2-3 times slower than JS in a similar code. What makes Go slow in this specific code?
go stdlib json encoding/decoding is incredibly slow, not sure for how much longer because there are drop in replacements now that I think are just as strict and feature parity.
-
Go with Chi has more ram consumption and less req/s than Koa or Fastify
3rd party JSON libraries could help if you were comparing JSON. https://github.com/goccy/go-json
-
ogen: spec-first OpenAPI v3 codegen for Go
However, I understand the code that is generated is super optimized. For example, rather than use a router, it does a static code generated router. Rather than use goccy/go-json, it does manual marshalling.
-
japi is a JSON HTTP API go library with generics
Minimal dependencies: julienschmidt/httprouter and goccy/go-json
-
Using a json lib other than encoding/json
I suggested using https://github.com/goccy/go-json at my work, since its a drop in replacement for the standard lib, but there are people who apprehensive. In my opinion the performance gains are significant to justify adoption. But I'd like your input.
- Whats the fastest JSON unmarshaling package as of right now?
-
What are your favorite packages to use?
go-json for encoding/decoding
pflag
-
issue with pflag flagset
My understanding is that you can use pflag as a drop in replacement of the standard lib's flag (import flag "github.com/spf13/pflag"). So it can be used as a standalone lib I suppose.
-
Which packages do you recommend for building cli tools?
I realy enjoyed the patched version from spf13 with "--" support https://github.com/spf13/pflag
-
Define custom command-line flag types in Go 1.19
Nice, but Cobra (with pflag underneath) is so, so better.
-
-h --help -help help --? -? ????
Not by default on stdlib. There are libraries available though - https://github.com/spf13/pflag
-
Coral, a friendly Cobra fork with nearly all its features, but only 4 dependencies
Flag functionality is provided by the pflag library, a fork of the flag standard library which maintains the same interface while adding POSIX compliance.
-
xflags: An approach to command line flags with support for subcommands, positional args, environment variables, etc.
How does it compare to https://github.com/spf13/pflag ?
-
The flag package: strange but good?
spf13 has a drop in pflag that does the - short and -- long flags.
-
What are your favorite packages to use?
oklog/ulid to generate IDs. coreos/go-oidc for validating JWTs I get from auth. google/go-cmp for comparing structs in tests (unless the project is already using Testify). spf13/pflag because life's too short for Go's flag handling. getkin/kin-openapi for validating reqests/responses against my OpenAPI spec (in tests).
-
akamensky/argparse: Argparse for Golang. Just because "flag" sucks!
What are the benefits of this package over the widely used spf13/pflag?
-
Go’s highly modular nature makes it particularly good for situations where requirements are changing or evolving.
3
What are some alternatives?
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
flag - Flag is a simple but powerful command line option parsing library for Go support infinite level subcommand
easyjson - Fast JSON serializer for golang.
cobra - A Commander for modern Go CLI interactions
GJSON - Get JSON values quickly - JSON parser for Go
kingpin - CONTRIBUTIONS ONLY: A Go (golang) command line and flag parser
go-fuzz - Randomized testing for Go
go-flags - go command line option parser
Gin - Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
complete - bash completion written in go + bash completion for go command
zap - Blazing fast, structured, leveled logging in Go.
argparse - Argparse for golang. Just because `flag` sucks