NDJSON, which actually has a rudimentary spec, says > Each JSON text MUST conform to the [RFC8259] standard and MUST be written to the stream followed by the n

NDJSON, which actually has a rudimentary spec, says > Each JSON text MUST conform to the [RFC8259] standard and MUST be written to the stream followed by the newline character \n (0x0A). https://github.com/ndjson/ndjson-spec/ https://github.com/ndjson/ndjson-spec/ But yeah, these things should be merged and formalized. Being web-adjacent, how likely is that? What we're seeing here is the usual patterns: - the less-useful newer thing with slightly better marketing wins eyeballs even when it's technically inferior - an "ecosystem cornerstone" is someone's pet project from a prior employer and now neglected (https://github.com/ndjson/ndjson-spec/issues/35#issuecomment-1285673417 https://github.com/ndjson/ndjson-spec/issues/35#issuecomment...) - web things don't get RFCs written because web people are disconnected from old school internet people - W3C adjacent people didn't get their RDF tuple world domination and industry standards don't matter to them - even MDN is switching to paywalls instead of being a useful resource