fp.

> Introducing the ‘packed’ data format, a binary format that allows using data as it is, without the need for a deserialisation step. A notable perk of this format is that traversals on packed trees is proven to be faster than on ‘unpacked’ trees: as the fields of data structures are inlines, there are no pointer jumps, thus making the most of the L1 cache.

That is, a "memory dump -> zero-copy memory read" of a subgraph of Haskell objects, allowing to pass such trees / subgraphs directly over a network. Slightly reminiscent of Cap'n Proto.

90s_dev•10mo ago

We are always reinventing wheels. If we didn't, they'd all still be made of wood.

Zolomon•10mo ago

They mention this in the article.

spockz•10mo ago

It reminds me more of flat buffers though. Does protobuf also have zero allocation (beyond initial ingestion) and no pointer jumps?

cstrahan•10mo ago

No, one example of why being variable sized integers.

See https://protobuf.dev/programming-guides/encoding/

carterschonwald•10mo ago

One thing that sometimes gets tricky in these things is handling Sub term sharing. I wonder how they implemented it.

tlb•10mo ago

> the serialised version of the data is usually bigger than its in-memory representation

I don’t think this is common. Perhaps for arrays of floats serialized as JSON or something. But I can’t think of a case where binary serialization is bigger. Data types like maps are necessarily larger in memory to support fast lookup and mutability.

nine_k•10mo ago

I suppose all self-describing formats, like protobuf, or thrift or, well, JSON are bigger than the efficient machine representation, because they carry the schema in every message, one way or another.

IsTom•10mo ago

If you use a lot of sharing in immutable data it can grow a lot when serializing. A simple pathological example would be a tree that has all left subtrees same as the right ones. It takes O(height) space in memory, but O(2^height) when serialized.

gitroom•10mo ago

honestly i wish more stuff worked this way - fewer hops in memory always makes me happy

lordleft•10mo ago

This was very well written. Excellent article!

NetOpWibby•10mo ago

Is this like MessagePack for Haskell?

Motorola GrapheneOS devices will be bootloader unlockable/relockable

Developer Certificate of Origin and AI is a no-go

Wait what, you can't use a *code* editor when you're under 18 now?

Show HN: PreflightAPI – US airports, weather, NOTAMs and more via one API

Show HN: Formualizer – Arrow-backed spreadsheet engine, 320 functions,PyO3+WASM

Left-Handers Are More Competitive Than Right-Handers

The Markless Document Markup Standard

People Really Are More Likely to Commit Crimes After a Cancer Diagnosis

Show HN: Restless – a CLI that discovers and maps APIs automatically

Four months of Ruby Central moving Ruby backward

Trump Worries Iran's Leaders May Be Just 'As Bad' After War

Anatomy of a Web3 Supply Chain Attack

Windows 98 Disk Defrag Simulator

3M Canadian Adults Taking GLP-1 Drugs, Reshaping Eating and Spending Habits

Claude's Cycles [pdf]

Haptics: Tactile Feedback for the Mobile Web

Offshore Wind Turbine Will House a Data Center Underwater

Intel appoints noted technologist Dr. Craig Barratt as Board achair

OpenAI is developing alternative to Microsoft's GitHub

Scaling up enhanced rock weathering for equitable climate change mitigation

Sam Altman says OpenAI is renegotiating Pentagon 'opportunistic and sloppy' deal

Show HN: I built a LLM human rights evaluator for HN (content vs. site behavior)

The Supreme Court doesn't care if you want to copyright your AI-generated art

Google Chrome switches to two-week release cycle

ChatGPT Health 'under-triaged' half of medical emergencies in a new study

Universal-3 Pro Streaming

Show HN: Dracula-AI – A lightweight, async SQLite-backed Gemini wrapper

Show HN: Sovereign Trace Stamp – Frozen triple-time cryptographic timestamp

Cancel ChatGPT AI boycott surges after OpenAI pentagon military deal

Show HN: Demarkus – De-centralized Markup for Us:memory for AI agents and humans