goprotobuf VS go-capnproto

Compare goprotobuf vs go-capnproto and see what are their differences.

goprotobuf

Go support for Google's protocol buffers (by golang)

go-capnproto

Cap'n Proto library and parser for go. This is go-capnproto-1.0, and does not have rpc. See https://github.com/zombiezen/go-capnproto2 for 2.0 which has rpc and capabilities. (by glycerine)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
goprotobuf go-capnproto
13 0
9,508 288
0.5% -
2.8 0.0
11 days ago about 4 years ago
Go Go
BSD 3-clause "New" or "Revised" License GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

goprotobuf

Posts with mentions or reviews of goprotobuf. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-08-19.
  • Protoc Plugins with Go
    2 projects | dev.to | 19 Aug 2023
    Now let’s take a look at the source code of the protoc-gen-go plugin:
  • How Turborepo is porting from Go to Rust
    7 projects | news.ycombinator.com | 21 Jul 2023
  • The Tragic Death of Inheritance
    2 projects | /r/programmingcirclejerk | 5 Jul 2023
    Wait, you say, in Go you can embed a struct with default method implementations to "inherit" them in your composed struct... sure, except any methods called by those methods are early-bound in the original struct, completely ignoring your wrapper, so the best you can do is "not implemented" rather than actually implement something. It is at least a way to prevent semver-major breakage, which the gRPC generator uses, but that's about as far as it gets you.
  • 2022-01-11 gRPC benchmark results
    3 projects | /r/grpc | 12 Jan 2022
    Seems like go is pretty middle of the road. I can only guess as to why but it probably has to do with heavy usage of pointers and reflection which are much slower than other implementations. Gogo/protobuf (RIP) solved this performance with code generation, but the the official go protobuf implementation has essentially eschewed it. I do wonder how the benchmark would look using the new vitess proto library for Go (which has many of the benefits of gogo but with active development and an API built on top of the Google one)
  • A complete yet beginner friendly guide on how to secure Linux
    17 projects | /r/linux | 4 Jun 2021
    go get github.com/golang/protobuf/protoc-gen-go
    17 projects | /r/linux | 4 Jun 2021
  • A new ProtoBuf generator for Go
    7 projects | news.ycombinator.com | 3 Jun 2021
    Maybe I'm missing something, but my read of [golang/protobuf#364](https://github.com/golang/protobuf/issues/364) was that the re-organization in protobuf-go v2 was allow for optimizations like gogoprotobuf to be developed without requiring a complete fork. I totally understand that the authors of gogoprotobuf do not have the time to re-architect their library to use these hooks, but best I can figure this generator does not use these hooks either. Instead it defines additional member functions, and wrappers that look for those specialized functions and fallback to the generic ones if not found.

    I am thinking about stuff like the [ProtoMethods](https://pkg.go.dev/google.golang.org/[email protected]/reflec...) API.

    I wonder why not? Did the authors of the vtprotobuf extension not want to bite off that much work? Is the new API not sufficient to do what they want (thus failing some of the goals expressed in golang/protobuf#364?

  • How to Auto Generate JavaScript code using GO
    2 projects | /r/golang | 9 May 2021
    In this case try approach with line by line generation. Very much like what protoc-gen-go does for Go code: https://github.com/golang/protobuf/blob/ae97035608a719c7a1c1c41bed0ae0744bdb0c6f/protoc-gen-go/grpc/grpc.go#L142, need to implement this kind of generator yourself.
  • Writing a code generator in Go
    3 projects | /r/golang | 26 Apr 2021
    Something like this: https://github.com/golang/protobuf/blob/master/internal/gengogrpc/grpc.go
  • The State of Go Plugins
    5 projects | dev.to | 18 Feb 2021
    The difference to the client-server solution is subtile when it comes to the details in implementation. protoc-gen-go and other plugins in the Protocol Buffers ecosystem use this approach.

go-capnproto

Posts with mentions or reviews of go-capnproto. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning go-capnproto yet.
Tracking mentions began in Dec 2020.

What are some alternatives?

When comparing goprotobuf and go-capnproto you can also consider the following projects:

colfer - binary serialization format

gogoprotobuf - [Deprecated] Protocol Buffers for Go with Gadgets

jsoniter - A high-performance 100% compatible drop-in replacement of "encoding/json"

cbor - CBOR codec (RFC 8949) with CBOR tags, Go struct tags (toarray, keyasint, omitempty), float64/32/16, big.Int, and fuzz tested billions of execs.

mapstructure - Go library for decoding generic map values into native Go structures and vice versa.

asn1

buf - The best way of working with Protocol Buffers.

csvutil - csvutil provides fast and idiomatic mapping between CSV and Go (golang) values.