I agree with all you have said, but I stick to my point, text is a just a binary format we have agreed upon to decode individual characters then secondary decod

I agree with all you have said, but I stick to my point, text is a just a binary format we have agreed upon to decode individual characters then secondary decoders are built upon that. Since we have agreed on this binary format for characters there is a viewer for this format built into almost everything, hence its convenience. If we agreed upon a binary format that encodes hierarchal nodes/key/values with various data types (raw binary, strings, numbers, dates) then hopefully there would be a similar viewer everywhere and no need for most secondary decoders (json on top of text). It should also be faster and more compact if sending binary or numbers or dates. Properly designed it should still be able to handle corruption, but that just has a lot to with the decoder and how it handles the corruption.