From XML to JSON to CBOR

Post by flowerthoughts » Fri, Aug 01, 2025, 6:34 AM UTC

eadmund wrote: post #81

flowerthoughts wrote: post #79

Earlier quoted context omitted.

The ASN.1 notation wasn't meant for parsing. And then people started writing parsing generators for it, so they adapted. However, you're abusing a text format for human reading and pretending it's a serialization format. The BER/PER are binary formats and great where binary formats are needed. You also have XER (XML) and JER (JSON) if you want text. You can create an s-expr encoding if you want. Separate ASN.1--the d…

> However, you're abusing a text format for human reading and pretending it's a serialization format. They should be the same, in order to facilitate human debugging. And we were discussing ASN.1, not its serialisations. Frankly, I thought that it was fairer to compare the S-expression to ASN.1, because both are human-readable, rather than to an opaque blob like: MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDrEee0Ri4Juz+Qfi…

Post by eadmund » Fri, Aug 01, 2025, 10:01 AM UTC

flowerthoughts wrote: post #101

eadmund wrote: post #81

Earlier quoted context omitted.

> However, you're abusing a text format for human reading and pretending it's a serialization format. They should be the same, in order to facilitate human debugging. And we were discussing ASN.1, not its serialisations. Frankly, I thought that it was fairer to compare the S-expression to ASN.1, because both are human-readable, rather than to an opaque blob like: MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDrEee0Ri4Juz+Qfi…

> And we were discussing ASN.1, not its serialisations. You said >> Would you rather write a parser for this: which suggested you were talking about serializations. I apologize if I misunderstood.

Post by naikrovek » Sat, Aug 02, 2025, 1:59 AM UTC

hvb2 wrote: post #62

naikrovek wrote: post #50

Earlier quoted context omitted.

i write my own binary formats because they're fast and small. yes, in production. partly because it's just as easy as anything else for me now, partly because it doesn't require any dependencies at all, and partly to show others just how easy it is, because i think people are unnecessarily afraid of this. no i don't write my own encoding or encryption. why the hell would anyone use json for everything, and why would…

I didn't say anywhere that we should use json for everything. I think most people would go with something standard and documented. If you work in a team it helps if you can hire people that are familiar with tech or can read up on it easily. And in general, unless you can show that your formatter is an actual hot path in need of optimization, you've just added another piece of code in need of care and feeding for no…