Salta al contenuto principale


The fact that 99% of my RPC and event serialization has to be done in json is blowing my mind.

Where did we go wrong??

“It’s so simple” they say, wtf?

in reply to mnl mnl mnl mnl mnl

🌶️ take: in a lot of ways, XML was and is better than JSON: it has far better tooling around it (schemas, XSLT, etc), and is still at least somewhat human readable… but everyone decided they hated all the angle brackets, so instead we got JSON.
Unknown parent

mnl mnl mnl mnl mnl

Depending on the use case:
- XML
- protobuf/flatbuf/any decent binary serialization (much easier to handle)

For readability and human consumption: YAML

Unknown parent

Kill cars for climate!
Do you have an alternative format in mind?
Questa voce è stata modificata (1 anno fa)
Unknown parent

mnl mnl mnl mnl mnl
@joesabin I’m kind of fine with code bloat, in the sense that we can build software that does a lot more. But json parsing is just… complex, feature-poor and json is an infuriating format and not even that readable to boot.
in reply to mnl mnl mnl mnl mnl

@mnl mnl mnl mnl mnl Do you have a favorite JSON-datamodel-like binary serialization out of JSONB, BSON, BJSON, UBJSON, CBOR, MessagePack, etc?

Asking partly because it's hilarious that we as a community haven't decided, in fact we're so undecided that at least two of these have IETF RFCs, and partly because you might actually have a preference and offer some insight. 😃

@Kill cars for climate!

#cerealization

in reply to mnl mnl mnl mnl mnl

@mnl mnl mnl mnl mnl @Kill cars for climate! I'm not the only person in the world who things that YAML is a nifty format for things that need to be read and possibly written by humans! yay!

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.