4 ms·
It is a 7 year old article without specifying alternatives to an "already solved problem." So HN, what are the best alternatives available today and why?
by dano 1y ago
It is a 7 year old article without specifying alternatives to an "already solved problem."
So HN, what are the best alternatives available today and why?
- deleted 1y ago[deleted]
- gsliepen 1y agoSomething like MessagePack or CBOR, and if you want versioning, just have a version field at the start. You don't require a schema to pack/unpack, which I personally think is a good thing.
- rapsey 1y agoThere are none, protobufs are great.
- nicce 1y agoDepends. ASN.1 is a beast and another industry standard, but unfortunately the best tooling is closed source.
- cryptonector 1y agoThere was ZERO PB tooling in 2000. Just write it for ASN.1 instead.
- thinkharderdev 1y agoSupport across languages etc is much less mature but I find thrift serialization format to be much nicer than protobuf. The codegen somehow manages to produce types that look like types I would actually write compared to the monstrosities that protoc generates.
- akavi 1y agoMentioned above: https://github.com/stepchowfun/typical https://github.com/stepchowfun/typical
- deleted 1y ago[deleted]
- mdhb 1y agoCBOR is probably the best and most standards compliant thing out there that I’m aware of. It’s the new default in a lot of IOT specs, it’s the backbone for deep space communication networks etc.. Maintains interoperability with JSON. Is very much battle tested in very challenging environments.