The first question I have when I see a new generic data encoding -- a question not answered anywhere on your site's front page -- is what advantages it has over

The first question I have when I see a new generic data encoding -- a question not answered anywhere on your site's front page -- is what advantages it has over the current incumbent (Protocol Buffers). I can write text-formatted Protobuf in any text editor, convert it to efficiently encoded binary, and parse it in dozens of languages with both first- and third-party libraries. Protobuf also has a JSON encoding for use in browsers, an ecosystem of tools such as linters and formatters, and the continued support of a large commercial entity. For use cases where Protobuf is too slow, there is Cap'n Proto and Flatbuffers. Why would I switch to your format, which seems to have extremely limited language support (Go only?), is significantly more complex (look at all those built-in data types!) and is supported by a single person?