Top 15 Go Decoding Projects
🔍 Go tool for LSB steganography, capable of hiding any file within an image.
Go package containing implementations of efficient encoding, decoding, and validation APIs.Project mention: Rust vs. Go in 2023 | news.ycombinator.com | 2023-08-13
Further, Go refusing to have macros means that many libraries use reflection instead, which often makes those parts of the Go program perform no better than Python and in some cases worse. Rust can just generate all of that at compile time with macros, and optimize them with LLVM like any other code. Some Go libraries go to enormous lengths to reduce reflection overhead, but that's hard to justify for most things, and hard to maintain even once done. The legendary https://github.com/segmentio/encoding seems to be abandoned now and progress on Go JSON in general seems to have died with https://github.com/go-json-experiment/json .
Many people claiming their projects are IO-bound are just assuming that's the case because most of the time is spent in their input reader. If they actually measured they'd see it's not even saturating a 100Mbps link, let alone 1-100Gbps, so by definition it is not IO-bound. Even if they didn't need more throughput than that, they still could have put those cycles to better use or at worst saved energy. Isn't that what people like to say about Go vs Python, that Go saves energy? Sure, but it still burns a lot more energy than it would if it had macros.
Rust can use state-of-the-art memory allocators like mimalloc, while Go is still stuck on an old fork of tcmalloc, and not just tcmalloc in its original C, but transpiled to Go so it optimizes much less than LLVM would optimize it. (Many people benchmarking them forget to even try substitute allocators in Rust, so they're actually underestimating just how much faster Rust is)
Finally, even Go Generics have failed to improve performance, and in many cases can make it unimaginably worse through -- I kid you not -- global lock contention hidden behind innocent type assertion syntax: https://planetscale.com/blog/generics-can-make-your-go-code-...
It's not even close. There are many reasons Go is a lot slower than Rust and many of them are likely to remain forever. Most of them have not seen meaningful progress in a decade or more. The GC has improved, which is great, but that's not even a factor on the Rust side.
Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.
A simple, semantic and developer-friendly golang package for encoding&decoding and encryption&decryption
cross-platform, cli app to perform various operations on string
Package geom implements efficient geometry types for geospatial applications.
:steam_locomotive: Decodes url.Values into Go value(s) and Encodes Go value(s) into url.Values. Dual Array and Full map support. (by go-playground)
a package for decode form's values into struct in Go
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
Faster base64 encoding for Go (by cristalhq)
Simple and fast webp library for golang
json encoding and decoding (by go-faster)
A simple library to extract video and audio frames from media containers (based on libav).
Package polyline implements a Google Maps Encoding Polyline encoder and decoder.
Encoding and decoding for fixed-width formatted data
🛫 Fixed-Point Decimals
🔥 A Redis client for GoLang featuring Tags with Gob & JSON encoding. (by ainsleyclark)
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
What are some of the best open-source Decoding projects in Go? This list will help you: