The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
life
Posts with mentions or reviews of life.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-12-27.
-
Logger and Clean Architecture
This is why we wrote https://github.com/go-logr/life - it's the interface you can pass around while leaving the choice of implementation up to the topmost app layer. We include some implementation choices (zapr being one, and funcr being among the simplest) but that's not really the goal.
logr
Posts with mentions or reviews of logr.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-03-21.
- What is the common log library which is industry standard that is used in server applications?
-
Created a small logging library in Go.
logr
-
Logging Library
How about using https://github.com/go-logr/logr You’ll be able to swap concrete implementation easily which will allow you to try out different libs on the market without refactoring all your logic
-
Have you replaced Sirupsen/logrus, and if so, with what?
I recommend https://github.com/go-logr/logr and you can choose implementation freely but zerolog/zap are optimized for speed.
-
Version 1.18 Refresh for Go Programmers
For logging, I use https://github.com/go-logr/logr with https://github.com/uber-go/zap
- Golog: an extensible logger for Go
-
Logger and Clean Architecture
I'd say it depends. If I write a package for others to use I usually don't include a logger at all and let the user decide what he wants to use. For any other project that needs logging I usually skip the interface to not have the struggle with finding one interface that fits all at least logrus and zap. We kinda agreed at the team to just use zap by now. One.thing i wanted to try tho is using sth like logr which provides an interface for the most commonly used loggers.
-
Go Masterpieces
After writing a lot of libraries I really appreciate logr. There are plenty of times when my library needs to output debugging info, but it's not practical to do things like parse flags for verbosity level. With thus I can just log at a higher V level and be done with it.
What are some alternatives?
When comparing life and logr you can also consider the following projects:
log15 - Structured, composable logging for Go
zerolog - Zero Allocation JSON Logger
go-core
zap - Blazing fast, structured, leveled logging in Go.
golog - Golog is a production ready logger which support tracing and other custom behaviours out of the box. Blazing fast and simple to use.
logrus - Structured, pluggable logging for Go.
log - Structured logging package for Go.
afero - A FileSystem Abstraction System for Go
Benthos - Fancy stream processing made operationally mundane
tailscale - The easiest, most secure way to use WireGuard and 2FA.
esbuild - An extremely fast bundler for the web