RX random-access JSON format

“when I load a 192kHz recording to izotope RX I can literallu see the harmonics going up to 96kHz”

“I find Rx (js, java, C#, etc) to be overly complicated in general.”

“I started out with binary encodings first, but then realized it limits so many workflows.”

“Very similar to bittorrent's bencode. That has the benefit that it has a canonical encoding which this doesn't”

“And to consider that anyone else would fill their brain with the rules to decipher that”

“RX, however matches Lua/LuaJIT extremely well and should out-perform the JS Proxy based decoder using metatables.”

“RX can represent any value JSON can represent.”

“That benchmark is a fair comparison for a real-world production workload and use case.”

“there are cases where JSON is currently used where this is much better”

“it was actually a pretty good standalone format”

“rx preserves object key order, but still implements O(log2 N) lookups for object keys.”

“it might be a matter of cleaning up the docs a bit”

“The current implementation is pretty close to ideal when deciding to use this encoding.”

“this would work very well for any case where you have embedded databases of unstructured data”

“This system with RX will work better because I get the indexes built-in to the data file”

“It's the unique combination of properties that makes it interesting.”

“The documentation reference a “decode” function, and it’s imported to the example code, but it’s never called.”

“The 23,000x faster single-key lookup seems a bit misleading to me.”

“I was instantly suspicious that a “new better format” for serialization didn’t open with the input/output.”

“this is exactly the kind of use case that caused me to design this format”

“Low heap allocations when reading values is one of the main driving factors in this design!”

“when I realized it's actually a good standalone format”

“But with this format, I can use the text as-is with zero preprocessing and as a bonus my datasets are 18x smaller.”

“for my use cases, this is actually better”

“rx works very well as a kind of embedded database like sqlite, but completely unstructured like JSON”

“Also note it stores decimal in a very compact encoding (two varints for base and power of 10)”

“It's also quite odd to create a serialization format optimized for random access.”

“same document as my json compressed to 110kb, so this is not great... 2x the size of json after compression”

“Came to the same conclusion the moment I had to hunt to see the outputs”

“It doesn't seem the actual serialization format is specified?”

“lets you read it without putting all the entities on the heap”

“That's the part where something like RX with selective access actually matters.”

“The viewer is cool, took me a while to find the link to it though”

“That kind of feels a bit worst of both worlds. None of the space savings/efficiency of binary but also no human readability.”

“It has jq like queries built in and supports inputs with either rx or json.”

“This format really excels for use cases where large read-only build artifacts are queried by worker nodes like an embedded database.”

“it is not in fact a drop in replacement for JSON.parse”

“usually easier to read, write and maintain than regexp strings”

“Rx in particular tends to exceed that budget pretty quickly.”

“were pretty useful in this regard”