4 ms·
Previous discussion, leading with a comment from one of the protobuf authors: https://news.ycombinator.com/item?id=18188519 https://news.ycombinator.com/item?id
by evmar 7y ago
Previous discussion, leading with a comment from one of the protobuf authors: https://news.ycombinator.com/item?id=18188519 https://news.ycombinator.com/item?id=18188519
- finnthehuman 7y agoThe way dweis never responded to batmansmk was disappointing to say the least. kentonv was willing to engage on the points and came out much more reasonable in the whole thing.
- joshuamorton 7y agodweis isn't a designer, so he'd be the wrong person to answer those things. Sanjay, Jeff, and Kenton are probably the three best to answer such questions. Presumably the top few concerns for protos are wire performance (decode/encode speed and cost, wire size), compatibility for changes (what this suggestion just totally breaks), and cross language usability. Some other tradeoffs might be non-wire perf (I believe protos beat flatbuffers here, at the cost of worse on wire perf), but it's not clear that that was intentional.