I've been drafting a binary format for describing, storing, and transmitting data, mainly for future personal projects. I plan to write a parser for it eventually, but before investing more time, I'd like feedback on the design and whether the scope is unreasonable. The document is intended to cover a general-purpose binary data description and storage format. I'm aware that established options already exist, but I'm interested in exploring the design myself. What seems useful, confusing, overly complicated, or missing?
2 Answers
The format document seems fairly thorough, and its organization looks broadly like what you'd expect from a binary format specification. The biggest missing piece is the motivation: what problem is this solving, what are its main advantages, and why would someone choose it over established alternatives such as Protocol Buffers, Thrift, Avro, or Parquet? Explaining the intended use cases and trade-offs would make the design much easier to evaluate.
The shared document appears to be unavailable or the link may be broken. It would also help to give a short overview of the format in the post itself—especially whether it's meant for serialization, long-term storage, data interchange, or some combination of those. A clearer description than just “binary serialization format” would help readers understand what they're reviewing.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically