encoding

Go package containing implementations of efficient encoding, decoding, and validation APIs. (by segmentio)

Encoding Alternatives

Similar projects and alternatives to encoding

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better encoding alternative or higher similarity.

encoding reviews and mentions

Posts with mentions or reviews of encoding. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-07.
  • Handling high-traffic HTTP requests with JSON payloads
    5 projects | /r/golang | 7 Dec 2023
  • Rust vs. Go in 2023
    9 projects | news.ycombinator.com | 13 Aug 2023
    https://github.com/BurntSushi/rebar#summary-of-search-time-b...

    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.

  • Quickly checking that a string belongs to a small set
    7 projects | news.ycombinator.com | 30 Dec 2022
    We took a similar approach in our JSON decoder. We needed to support sets (JSON object keys) that aren't necessarily known until runtime, and strings that are up to 16 bytes in length.

    We got better performance with a linear scan and SIMD matching than with a hash table or a perfect hashing scheme.

    See https://github.com/segmentio/asm/pull/57 (AMD64) and https://github.com/segmentio/asm/pull/65 (ARM64). Here's how it's used in the JSON decoder: https://github.com/segmentio/encoding/pull/101

  • 80x improvements in caching by moving from JSON to gob
    6 projects | /r/golang | 11 Apr 2022
    Binary formats work well for some cases but JSON is often unavoidable since it is so widely used for APIs. However, you can make it faster in golang with this https://github.com/segmentio/encoding.
  • Speeding up Go's builtin JSON encoder up to 55% for large arrays of objects
    2 projects | news.ycombinator.com | 3 Mar 2022
    Would love to see results from incorporating https://github.com/segmentio/encoding/tree/master/json!
  • Fastest JSON parser for large (~888kB) API response?
    2 projects | /r/golang | 7 Jan 2022
    Try this one out https://github.com/segmentio/encoding it's always worked well for me
  • 📖 Go Fiber by Examples: Delving into built-in functions
    4 projects | dev.to | 24 Aug 2021
    Converts any interface or string to JSON using the segmentio/encoding package. Also, the JSON method sets the content header to application/json.
  • In-memory caching solutions
    4 projects | /r/golang | 1 Feb 2021
    If you're interested in super fast & easy JSON for that cache give this a try I've used it in prod & never had a problem.
  • A note from our sponsor - SaaSHub
    www.saashub.com | 25 Apr 2024
    SaaSHub helps you find the best software and product alternatives Learn more →

Stats

Basic encoding repo stats
8
962
3.6
5 months ago

Sponsored
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com