zerolog

It can be useful to have zero-alloc libraries in Go, for use in larger programs that do allocate. See https://github.com/rs/zerolog for example.

I think Go's approach is similar - if you have a public repo, then whatever the DNS name is gives you a unique module name. For example, both of these modules can exist, and I can import both into a given Go project: github.com/rs/zerolog mysite.com/myforks/zerolog

Be aware that there is a performance impact compared to using zerolog directly [0] (my uneducated guess is it is likely due to pointer indirection). [0]: https://github.com/rs/zerolog/issues/571#issuecomment-166202...

Things I can't live without in a new Go project in no particular order: - https://github.com/golangci/golangci-lint - meta-linter - https://goreleaser.com - automate release workflows - https://magefile.org - build tool that can version your tools - https://godoc.org/github.com/ory/dockertest/v3 - run containers for e2e testing - https://github.com/ecordell/optgen - generate functional options - https://golang.org/x/tools/cmd/stringer - generate String() - https://mvdan.cc/gofumpt - stricter gofmt - https://github.com/stretchr/testify - test assertion library - https://github.com/rs/zerolog - logging - https://github.com/spf13/cobra - CLI framework FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/t

> At boundaries between our code and calls out to external packages, make an effort to always wrap the result with xerrors.Errorf. This ensures that we always capture a stack trace at the most proximate location of an error being generated as possible I've been doing something similar for a while, using `errors.WithStack` from https://github.com/pkg/errors The error can then be logged with https://github.com/rs/zerolog like this `log.Error().Stack().Err(err).Msg("")` For human readable output (instead of the standard JSON) use a console writer, see https://github.com/mozey/logutil

I've come across a fair share of zero-alloc implementations of various things, like u/poitrus' zerolog [0] and u/jorangreef's cuckoo-hashtable [1], for instance. Given that JavaScript runs on restrictive clients, it must have libraries in spades for this kind of a thing, but I couldn't find many. I'm really interested in techniques that are generally employed in languages like Java, Golang, Rust, C/++ that are worth translating over to JavaScript, especially now that TypedArrays are a reality. I'm pretty sure there's more to zero-alloc than just Buffers, Object pools, and Recyclables, but I can't seem to find good resources to get started with this. [0] https://github.com/rs/zerolog [1] https://github.com/ronomon/hash-table/blob/master/README.md

Nice work. I personally tend to favour zero-gc and fast loggers like this one: https://github.com/rs/zerolog

Interesting article but I am not sure about the recommendation of writing your own command parsing instead of using something like mow.cli[1] which seems fairly lightweight and self-contained. In terms of logging I am also wondering if something like zerolog[2] might be a better choice than go-kit's logger given its higher performance [1] https://github.com/jawher/mow.cli [2] https://github.com/rs/zerolog