compress
Testify
compress | Testify | |
---|---|---|
17 | 64 | |
4,506 | 22,073 | |
- | 1.1% | |
8.4 | 8.6 | |
21 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
Testify
-
What 3rd-party libraries do you use often/all the time?
github.com/stretchr/testify
-
Testing calls to Daily's REST API in Go
I then verify that there are no issues with writing the body with require.NoError() from the testify toolkit. This will ensure the test fails if something happens to go wrong at this point.
-
Gopher Pythonista #1: Moving From Python To Go
For testing purposes, Go provides a go test command that automatically discovers tests within your application and supports features such as caching and code coverage. However, if you require more advanced testing capabilities such as suites or mocking, you will need to install a toolkit like testify. Overall, while Go provides a highly effective testing experience, it's worth noting that writing tests in Python using pytest is arguably one of the most enjoyable testing experiences I have encountered across all programming languages.
- Why elixir over Golang
-
How to start a Go project in 2023
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://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/tree/main/tools/analyzers
-
Do you wrap testing libraries?
Im thinking in wrap or not the library https://github.com/stretchr/testify to do my tests.
-
[Go] How to unit test for exception handling?
Are you limited to the std lib, or can you use testify? You can require things like require.Error()
-
Tools besides Go for a newbie
IDE: use whatever make you productive. I personally use vscode. VCS: git, as golang communities use github heavily as base for many libraries. AFAIK Linter: use staticcheck for linting as it looks like mostly used linting tool in go, supported by many also. In Vscode it will be recommended once you install go plugin. Libraries/Framework: actually the standard libraries already included many things you need, decent enough for your day-to-day development cycles(e.g. `net/http`). But here are things for extra: - Struct fields validator: validator - Http server lib: chi router , httprouter , fasthttp (for non standard http implementations, but fast) - Web Framework: echo , gin , fiber , beego , etc - Http client lib: most already covered by stdlib(net/http), so you rarely need extra lib for this, but if you really need some are: resty - CLI: cobra - Config: godotenv , viper - DB Drivers: sqlx , postgre , sqlite , mysql - nosql: redis , mongodb , elasticsearch - ORM: gorm , entgo , sqlc(codegen) - JS Transpiler: gopherjs - GUI: fyne - grpc: grpc - logging: zerolog - test: testify , gomock , dockertest - and many others you can find here
-
Is gomock still maintained and recommended?
To answer OP directly, I am largely quite happy with mockery (and testify) to write expressive tests.
-
Golang, GraphQL y Postgress
Como herramientas te recomiendo: FastJson https://github.com/valyala/fastjson : Si necesitas leer jsons Testify https://github.com/stretchr/testify : Para mockear y testear
What are some alternatives?
nodejs-js-compress-benchmark - Benchmark NodeJS/JS compression libraries
ginkgo - A Modern Testing Framework for Go
go - The Go programming language
GoConvey - Go testing in the browser. Integrates with `go test`. Write behavioral tests in Go.
sqlite-zstd - Transparent dictionary-based row-level compression for SQLite
gomega - Ginkgo's Preferred Matcher Library
easyjson - Fast JSON serializer for golang.
gomock - GoMock is a mocking framework for the Go programming language.
jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"
gotest.tools - A collection of packages to augment the go testing package and support common patterns.
gzipped - Replacement for golang http.FileServer which supports precompressed static assets.
go-cmp - Package for comparing Go values in tests