JSON already complicated implementation pretty significantly compared to a binary format, and there is no apparent support for compression, integrity verificati

JSON already complicated implementation pretty significantly compared to a binary format, and there is no apparent support for compression, integrity verification, or encryption. You can layer those on tar.gz style of course, but then you don't get nice content lists without having to decompress the whole thing. It seems to me that the tradeoffs here make it suitable for relatively few use cases. Nothing wrong with that per-se, but I wouldn't call it "powerful" or even "simple"[0]. Also: I'm guessing the header_size field is LE and the header itself is null terminated but neither is necessarily true. Details like that should be specified. [0] Thinking about it some more, as long as your use case is "access from JavaScript" I guess "simple" does apply.