compress
nodejs-js-compress-benchmark
| compress | nodejs-js-compress-benchmark | |
|---|---|---|
| 17 | 1 | |
| 4,506 | 3 | |
| - | - | |
| 8.4 | 0.0 | |
| 21 days ago | about 3 years ago | |
| Go | TypeScript | |
| 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
nodejs-js-compress-benchmark
What are some alternatives?
go - The Go programming language
compression - Node.js compression middleware
sqlite-zstd - Transparent dictionary-based row-level compression for SQLite
best - :trophy: Delightful Benchmarking & Performance Testing
easyjson - Fast JSON serializer for golang.
snappy - Fastest Snappy compression library in Node.js
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
http_compression - 🗜️ Deno HTTP compression middleware
gzipped - Replacement for golang http.FileServer which supports precompressed static assets.
golang-http-handler-with-gzip - Golang HTTP Handler With Gzip
zap - Blazing fast, structured, leveled logging in Go.
wormhole-gui - Cross-platform application for easy encrypted file, folder, and text sharing between devices. [Moved to: https://github.com/Jacalz/rymdport]