go-cmp VS logrus

This made me think of a couple other interesting things:

1. you can change which algorithm is used in git diff as multiple are supported

https://luppeng.wordpress.com/2020/10/10/when-to-use-each-of...

2. Google has an edit graph implementation in Go in the cmp package

https://github.com/google/go-cmp/blob/master/cmp/internal/di...

Assertion libraries that people seem to love: - testify (my favorite) - go-cmp is a more barebones library - gotest.tools -- I have never used this but some swear by it

it uses https://github.com/google/go-cmp instead of reflect.DeepEqual

When I use functional arguments, I either prefix all of the options with the same prefix or put them in a dedicated package (like cmpopts) to help the IDE.

Checking for equality in tests: https://github.com/google/go-cmp

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).

One thing to keep in mind about reflect.DeepEqual is because of the way it is implemented you could get positive results when the values are not actually the same, see this comment for reference.

It's some sort of logging system well explained by Alex Edwards in Let’s Go Further. As stated, we could have used logrus or any other popular logging system in Go.

Option 2, please. You may not have been around for the logrus debacle, but it was a giant pain.

For the example I’m using the very popular logrus library and then I’m setting the log formatter to be JSON

For choosing the candidates for the poll, I didn't do any thorough research. I was looking for a library to use in my project at work, and I ended up at sirupsen/logrus which was already being used by one of the dependencies in that project.

I contribute to OSS as part of my job on the regular. The company is good about contributing upstream, signing CLAs, and all that. We still work against private forks for two main reasons: 1. Some changes that we need are not accepted by maintainers based on philosophical or architectural reasons that we can’t otherwise work around. You’re beholden to then unless you publicly fork the repo which has other legal/PR overhead for the company and OSS political implications. 2. Maintainers in the past have taken down repos, renamed repos, or changed the licensing on repos that have left us in a lurch. We always build against our own private forks because we need predictability and can’t be beholden to some other party for business continuity. We sync them down from the public upstream at our leisure.

If they change the case on their username on the other hand, the Go ecosystem explodes: https://github.com/sirupsen/logrus/issues/570#issuecomment-3...

Like, for example, some projects importing logrus with a capital L and some with a lowercase L, and go modules having no way to reconcile the two: https://github.com/sirupsen/logrus/issues/553

Ugh. Wish people would stop using logrus. It’s in maintenance mode and slow, especially its stack tracing.