compress
zap
compress | zap | |
---|---|---|
17 | 51 | |
4,506 | 20,981 | |
- | 1.0% | |
8.4 | 8.1 | |
22 days ago | 4 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | 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.
compress
- Chrome Feature: ZSTD Content-Encoding
-
Show HN: Gogosseract, a Go Lib for CGo-Free Tesseract OCR via Wazero
There's a pure-go zstd at https://github.com/klauspost/compress - it's likely faster than running the upstream zstd under Wazero.
-
When is go not a good choice?
It's no surprise that "fast" Go libraries are actually just assembly: https://github.com/klauspost/compress/blob/master/zstd/seqdec_amd64.s (just one file out of several, for just one architecture, for just one compression algorithm!)
-
zstd
There is a reasonably feature complete implementation of Zstd for Go: https://github.com/klauspost/compress/tree/master/zstd
It may not offer the same API 1:1, but it has no interoperability issues that I've encountered. So, I just think no one has bothered to implement it in Rust because most use cases don't mind the added bloat you're talking about. Plus, other comments I've seen suggest that you can actually tune the size of the zstd library, although I'm not sure if the Rust bindings expose that.
-
Medical image parser in Go
Thanks again for your review/comment!!! Btw, are you the author of this repo https://github.com/klauspost/compress because I love it!!!
-
Ask HN: Does https://github.com/klauspost/compress returns 502 for you?
I noticed Github returns "This page is taking too long to load" with status code 502 for https://github.com/klauspost/compress but rest of their urls works fine. Anyone know why would that be the case ?
Cloning the repo works perfectly well.
git clone https://github.com/klauspost/compress
- S2 Compression
-
Zstandard – Real-time data compression algorithm
Recent versions of zstd definitely don't obsolete LZ4, or else I don't think the author would still be contributing to both...
And if you're going to play with Snappy, you might find S2, which was linked on HN relatively recently, interesting. [1]
[1] - https://github.com/klauspost/compress/tree/master/s2
-
Restic 0.14.0 Released (with highly anticipated feature – compression)
Compression method appears to be zstandard and uses https://github.com/klauspost/compress, for those wondering like I was.
-
MinIO Object Placement Strategy in Distributed deployments
OMG u/klauspost is this you? https://github.com/klauspost/compress/tree/master/s2
zap
- Desvendando o package fmt do Go
-
Building RESTful API with Hexagonal Architecture in Go
The project currently uses slog package from standard library for logging. But switching to a more advanced logger like zap could offer more flexibility and features.
-
Structured Logging with Slog
It's nice to have this in the standard library, but it doesn't solve any existing pain points around structured log metadata and contexts. We use zap [0] and store a zap logger on the request context which allows different parts of the request pipeline to log with things like tenantid, traceId, and correlationId automatically appended. But getting a logger off the context is annoying, leads to inconsistent logging practices, and creates a logger dependency throughout most of our Go code.
[0] https://github.com/uber-go/zap
-
Kubebuilder Tips and Tricks
Kubebuilder, like much of the k8s ecosystem, utilizes zap for logging. Out of the box, the Kubebuilder zap configuration outputs a timestamp for each log, which gets formatted using scientific notation. This makes it difficult for me to read the time of an event just by glancing at it. Personally, I prefer ISO 8601, so let's change it!
-
Go 1.21 Released
What else would you expect from a structured logging package?
To me it absolutely makes sense as the default and standard for 99% of applications, and the API isn't much unlike something like Zap[0] (a popular Go structured logger).
The attributes aren't an "arbitrary" concept, they're a completely normal concept for structured loggers. Groups are maybe less standard, but reasonable nevertheless.
I'm not sure if you're aware that this is specifically a structured logging package. There already is a "simple" logging package[1] in the sodlib, and has been for ages, and isn't particularly fast either to my knowledge. If you want really fast you take a library (which would also make sure to optimize allocations heavily).
[0]: https://pkg.go.dev/go.uber.org/zap
[1]: https://pkg.go.dev/log
- Efficient logging in Go?
-
Why elixir over Golang
And finally for structured logging: https://github.com/uber-go/zap
-
Beginner-friendly API made with Go following hexagonal architecture.
For logging: I recommend using Uber Zap https://github.com/uber-go/zap It will log stack backtraces and makes it super easy to debug errors when deployed. I typically log in the business logic and not below. And log at the entry for failures to start the system. Maybe not necessary for this example, but it’s an essential piece of any API backend.
- slogx - slog package extensions and middlewares
- Why it is so weirdo??
What are some alternatives?
nodejs-js-compress-benchmark - Benchmark NodeJS/JS compression libraries
logrus - Structured, pluggable logging for Go.
go - The Go programming language
zerolog - Zero Allocation JSON Logger
sqlite-zstd - Transparent dictionary-based row-level compression for SQLite
slog
easyjson - Fast JSON serializer for golang.
glog - Leveled execution logs for Go
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
go-log - a golang log lib supports level and multi handlers
gzipped - Replacement for golang http.FileServer which supports precompressed static assets.
log - Structured logging package for Go.