Cap'n Proto 0.6 released – 2.5 years of improvements
This might be a contrarian view, maybe I&#x27;m misunderstanding it. To me, much of message passing is not performance critical, so it would be well served by JSON&#x2F;YAML&#x2F;XML for easy implementation&#x2F;testing&#x2F;debugging. If one needs performance, he can just send bytes over, which can be (de)serialised in a (couple) dozen SLOC. Sure, when you&#x27;re talking about very complex structures, RPC, dynamic schemas etc., then you might opt for something like this, but let&#x27;s be honest - that&#x27;s quite a minority of current users, isn&#x27;t it?<p>I never minded these frameworks, but then I wanted to write a few parsers for some file formats and they used Thrift&#x2F;Flatbuffers to encode a few ints, which seemed like a major overkill. There was no RPC, no packet loss, no nothing.