pp
versioninfo
| pp | versioninfo | |
|---|---|---|
| 3 | 6 | |
| 1,778 | 234 | |
| - | - | |
| 0.7 | 3.7 | |
| about 1 year ago | 9 months ago | |
| Go | Go | |
| MIT License | 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.
pp
-
How do you iterate though nested structs and print them?
for debug I use https://github.com/k0kubun/pp
- Libraries you use most of your projects?
versioninfo
-
Libraries you use most of your projects?
Oh, also https://github.com/carlmjohnson/versioninfo . Always need that.
-
FreePad | A free self-hosted pad written in go
Don’t. It’s obsolete. Just use debug.ReadBuildInfo()
-
Makefile and Dockerfile best practices
That’s obsolete. See https://github.com/carlmjohnson/versioninfo. Even if it weren’t, Make is an inappropriate tool. Because it is based on file modtimes, it can’t react to git hash changes. You just have rerun the steps every time, at which point Bash is a less awful language.
-
How to embed version when `go install`-ing (since you cannot use go:generate or ldflags -X)
Go 1.18 updates the debug info to also include the git status of the build. See https://github.com/carlmjohnson/versioninfo
-
Go 1.18 - debug/info - why not include the current git tag?
I use this trick in my versioninfo package. Obviously, it can't give you other tags, but most of the time the tag you want to know about is v1.2.3 anyway, and since tags are mutable but the Go sum DB is immutable, this is safer than just saying what tag was on disk at build time.
-
Getting excited for Go 1.18's lesser known features
I subscribed to GH activity for the correspondence friendliness-enhancing library by the author:
https://github.com/carlmjohnson/versioninfo/
The primary motivation curiousity to learn if this becomes "the [best/default] way" folks reach for when leveraging BuildInfo to deliver explicit binary versioning.
What are some alternatives?
logrus - Structured, pluggable logging for Go.
assert - A simple assertion library using Go generics
spew - Implements a deep pretty printer for Go data structures to aid in debugging
FreePad - FreePad is a simple Go project to help you juggle temporary notes that you might wanna pass from one device to another, or from a person to another with memorable and easy to communicate online "Pads".
log15 - Structured, composable logging for Go
flagx - Extensions to the Go flag package
go-logger - Simple logger for Go programs. Allows custom formats for messages.
logex - An golang log lib, supports tracking and level, wrap by standard log lib
logutils - Utilities for slightly better logging in Go (Golang).
logxi - A 12-factor app logger built for performance and happy development
backoff - ⏱ The exponential backoff algorithm in Go
glog - Leveled execution logs for Go