{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-01-19\n📝 Original message:The engineers at Google were well aware that ASN.1 existed. I can assure\nyou of that, because I was one of them.\n\nThe protobuf FAQ has a very polite take on the matter:\n\n   https://developers.google.com/protocol-buffers/docs/faq\n\nThis email thread gives more enlightenment:\n\n   https://groups.google.com/forum/#!topic/protobuf/eNAZlnPKVW4\n\nAnyone who has actually had to work with both ASN.1 and protocol buffers\nwill be able to explain why ASN.1 should not be chosen for any modern\nformats. A lot of it boils down to simplicty and quality of\nimplementations, especially open source implementations.\n\nWith respect to the specific concerns Richard raises:\n\nPerformance doesn't feel that relevant when you think that:\n\u003e\n\nPerformance wasn't a concern.\n\n\n\u003e 2. One would be cramming this data into a binary format just so you can\n\u003e then attach it to a no-so-binary format such as HTTP.\n\u003e\n\nHTTP transmits files as binary on the wire. So it's binary-clean and,\nmoreover, HTTP/2 aka SPDY is fully binary and doesn't use text anywhere\nexcept the gzip dictionary.\n\n\n\u003e 2. There are tons of great open source libraries and API for parsing /\n\u003e manipulating / generating.\n\u003e\n\nLuckily, this is also true of protocol buffers. Language support is pretty\ngood these days.\n\n\n\u003e 4. The standards are much easier to read and write. They don't need to\n\u003e contain code like BIP-0070 currently does and they can contain examples,\n\u003e which BIP70 does not.\n\u003e\n\nBIP 70 doesn't contain any code, as far as I know. The protobuf schema\nmight look like code, but it's not - it's just a description of what fields\na message can contain and their types. This is very relevant for a\nspecification!\n\nJSON in particular is pretty awful and I don't like it much. It suffers\ncomplexities with things as basic as encoding numbers and strings. It's\nvery much unsuited to applications where correctness matters and where\nyou're dealing with binary structures.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150119/e6a76662/attachment.html\u003e"}