Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I've used both cobra and cli, both are good. cli may be, IMO, a bit "lighter", not speed-wise (maybe it's different, but I haven't noticed), but it's not as feature-rich as cobra, but it's excellent.
I've used both cobra and cli, both are good. cli may be, IMO, a bit "lighter", not speed-wise (maybe it's different, but I haven't noticed), but it's not as feature-rich as cobra, but it's excellent.
I switched all from viper to kong.
At least for smaller apps, I like commando because it's light in terms of dependencies, it's straight-forward to use and parses getopt style parameters.
I personally swear by the go-arg package, as i prefer its library-not-framework approach.
Personally, I went with Cobra and Viper because they are used in so many big tools.
Related posts
- K3S Binary, How does that work?
- GoConsole: New Update! thanks all of you for your advice and your help.
- Title: GoConsole: a lightweight Go module for creating command-line commands
- climate "CLI Mate": a CLI library that autogenerates CLIs from structs / functions with support for nested subcommands, global / local flags, help generation from godocs, typo suggestions, shell completion and more
- Which packages do you recommend for building cli tools?