<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Benchmarking JSON BinPack · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2211.12799/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2211.12799/feed.xml" rel="self" type="application/rss+xml" /><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=41776978</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:41776978</guid><pubDate>Tue, 08 Oct 2024 13:10:33 GMT</pubDate><description>&lt;p&gt;Great stuff! I&amp;#x27;m starting to work a lot on the satellite space (https://www.sourcemeta.com), building a binary serialization format around JSON called JSON BinPack (https://jsonbinpack.sourcemeta.com) that is extremely space-efficient to pack more documents in the same Iridium uplink/downlink operation (up to 74% more compact than Protocol Buffers. See reproducible benchmark here: https://arxiv.org/abs/2211.12799). It is still a heavy work in progress, but if anybody here is suffering from expensive Iridium bills, I would love to connect and discuss to make sure JSON BinPack is built the…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=41697031</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:41697031</guid><pubDate>Mon, 30 Sep 2024 13:47:52 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;m working on JSON BinPack (https://jsonbinpack.sourcemeta.com), a binary serialization format for JSON (think of it as a Protobuf alternative) with a strong focus on space-efficiency for reducing costs when transferring structured data over 5G and satellite transceivers for robotics, IoT, automotive, etc. If you work at any of those industries and pay a lot for data transfer, please reach out! I&amp;#x27;m trying to talk to as many people as possible to make sure JSON BinPack fits their use case well (I&amp;#x27;m trying to build a business around it). It was originally designed during my (award-winning!)…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=41300327</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:41300327</guid><pubDate>Tue, 20 Aug 2024 14:21:35 GMT</pubDate><description>&lt;p&gt;We do! See https://benchmark.sourcemeta.com for a live benchmark and https://arxiv.org/abs/2211.12799 for a more detailed academic benchmark. The TLDR is that is that if you use JSON BinPack on schema-less mode, its still more space-efficient than MessagePack but not by a huge margin (depends on the type of data of course). But if you start passing a JSON Schema along with your data, the results become way smaller. Please reach out to jv@jviotti.com. I would love to discuss your use case more.&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=41294564</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:41294564</guid><pubDate>Mon, 19 Aug 2024 21:02:17 GMT</pubDate><description>&lt;p&gt;CBOR is a schema-less binary format. JSON BinPack supports both schema-less (like CBOR) and schema-driven (with JSON Schema) modes. Even on the schema-less mode, JSON BinPack is more space-efficient than CBOR. See https://benchmark.sourcemeta.com for a live benchmark and https://arxiv.org/abs/2211.12799 for a more detailed academic benchmark&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=41293285</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:41293285</guid><pubDate>Mon, 19 Aug 2024 18:08:51 GMT</pubDate><description>&lt;p&gt;Very cool! How are the balloons transferring telemetry back to earth for analysis, etc? Asking because my research at the University of Oxford was around hyper space-efficient data transfer from remote locations for a fraction of the price. The result was an award-winning technology (https://jsonbinpack.sourcemeta.com) to serialise plain JSON that was proven to be more space-efficient than every tested alternative (including Protocol Buffers, Apache Avro, ASN.1, etc) in every tested case (https://arxiv.org/abs/2211.12799). If it&amp;#x27;s interesting, I&amp;#x27;d love to connect and discuss (jv@jviotti.com)…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=40390994</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:40390994</guid><pubDate>Fri, 17 May 2024 15:31:59 GMT</pubDate><description>&lt;p&gt;I&amp;#x27;m currently building a Protocol Buffers alternative that uses JSON Schema instead: https://jsonbinpack.sourcemeta.com/. It was proven on research to be as or more space-efficient than any considered alternative (https://arxiv.org/abs/2211.12799). However, it is still heavily under development and not ready for production use. Definitely looking for GitHub Sponsors or other type of funding to support it :)&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — mentioned by jviotti</title><link>https://news.ycombinator.com/item?id=36932604</link><guid isPermaLink="false">urn:hackerpapers:mention:2211.12799:36932604</guid><pubDate>Sun, 30 Jul 2023 16:00:37 GMT</pubDate><description>&lt;p&gt;If you are interested in learning more about binary serialization (for Cap&amp;#x27;n Proto and others), I wrote two free-to-read papers extensively looking at the scene from a space-efficiency point of view that people here might be interested in: - https://arxiv.org/abs/2201.02089 - https://arxiv.org/abs/2201.03051 Not something that aims to compete with Cap&amp;#x27;n Proto (different use cases), but I&amp;#x27;ve been also working on a binary serialization format that is pure JSON-compatible with a focus on space-efficiency: https://www.jsonbinpack.org. Benchmarks here: https://arxiv.org/abs/2211.12799&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item><item><title>Benchmarking JSON BinPack — HN submission</title><link>https://news.ycombinator.com/item?id=33745660</link><guid isPermaLink="false">urn:hackerpapers:submission:2211.12799:33745660</guid><pubDate>Fri, 25 Nov 2022 19:01:37 GMT</pubDate><description>&lt;p&gt;Benchmarking JSON BinPack&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;2 points; 0 discussion replies on HN. &lt;a href="https://hackerpaper.kaipfister.de/p/2211.12799/"&gt;Paper and source history&lt;/a&gt;. A submission is not an endorsement.&lt;/p&gt;</description><category>cs.SE</category></item></channel></rss>
