4 ms·
maybe if performance is really an issue, protobufs shouldn't be used ? there is also flatbuffers, capnp and purely C++ serializers: zpp, yas... but protobufs a
by dgan 1y ago
maybe if performance is really an issue, protobufs shouldn't be used ?
there is also flatbuffers, capnp and purely C++ serializers: zpp, yas... but protobufs are definitely convenient !
- philwelch 1y agoIf performance isn’t an issue, why not JSON?
- foobiekr 1y agoperformance is always an issue when the alternative is 2+ orders of magnitude slower.
- 9rx 1y agoProtobuf tooling isn't great, but JSON tooling is far worse. Developer experience matters too. (Technically protobuf supports JSON encoding, but its additional work to enable, again diminishing the developer experience)
- 9rx 1y agoIf execution performance is really that much of an issue you're not going to choose Go anyway, rendering this project moot. What is a real issue is marketing performance. As it turns out, everyone loves a story about something going fast. So it pays to create these kinds of optimizations for the sake of the story, used to sell the product to the developer who makes choices based on what they think feels good.