Onion VS FlatBuffers

I've also recently fallen into (reading/watching about) it, and from what I've seen, some of them have really impressive levels of community software support

e.g. https://onionui.github.io

OnionOS is your best choice. It's as simple as dropping the files onto your SD card. Then, moving your game files to their respective folders. Here is a video guide. Here is the official page with download and any information you would need. If you're still using the stock card, I'd highly recommend getting a better quality one so that you don't lose all your data again.

Download Onion OS to your computer. Onion OS is available from the link below: https://onionui.github.io/

Update PixelReader to v0.6 by @Aemiii91 in #1208

(Please note that I am using Onion OS V4.2.0-RC, if you are using other version, it may not work.

I followed the instructions from here and used the specialized software. It's a Samsung Pro Evo SD card bought in an official store and the reduction is completely reversible by using the Windows formatter. I don't really mind that much, but am wondering if I didn't noob myself out of twice as much space!

I don't work at Cloudflare but follow their work and occasionally work on performance sensitive projects.

If I had to guess, they looked at the landscape a bit like I do and regarded Cap'n Proto, flatbuffers, SBE, etc. as being in one category apart from other data formats like Avro, protobuf, and the like.

So once you're committed to record'ish shaped (rather than columnar like Parquet) data that has an upfront parse time of zero (nominally, there could be marshalling if you transmogrify the field values on read), the list gets pretty short.

https://capnproto.org/news/2014-06-17-capnproto-flatbuffers-... goes into some of the trade-offs here.

Cap'n Proto was originally made for https://sandstorm.io/. That work (which Kenton has presumably done at Cloudflare since he's been employed there) eventually turned into Cloudflare workers.

Another consideration: https://github.com/google/flatbuffers/issues/2#issuecomment-...

Much more in the discussion of this particular issue onGitHub: flatbuffers:Reverse engineering #4258

Related but not Rust-specific: FlatBuffers, Cap'n Proto.

If json files are a concern because of space, you can always look into something like protobuffers or flatbuffers. But whatever you use, you should try to find a solution where you don't have to think about the actual serialization/deserialization of your objects, and can just concentrate on the data.

Or, as an alternative to protobuffers, there's also flatbuffers, which is lighter weight and needs less memory: https://google.github.io/flatbuffers/

As the title suggests, I am considering using Flatbuffers as a way to parse sensor data that has been stored in local datafiles. The project language is python.