# Lite³

14 Hacker News commenters recommended Lite³ and 6 criticized it, November 2025 to November 2026. It was recommended in 3 of 13 months.

**Verdict:** Fast zero-copy access to indexed, JSON-like data that can be edited in place, though critics say its wire format is not JSON-compatible.

## Why people recommend it

- Much faster than JSON parsing (3 comments): "It is like sending a mini-database that can be queried at speeds thousands of times faster than any JSON library is able to parse." ([source](https://news.ycombinator.com/item?id=46250695)) "you don't need to do any parsing, since the document itself is already indexed" ([source](https://news.ycombinator.com/item?id=46248131)) "is able to outperform simdjson by 120x in some benchmarks as a result" ([source](https://news.ycombinator.com/item?id=46507948))
- Promising for databases and tools (3 comments): "I think databases is where this technology will eventually have the greatest potential" ([source](https://news.ycombinator.com/item?id=46325434)) "Building a jq around something like Lite^3 or JSONB is a very appealing thought." ([source](https://news.ycombinator.com/item?id=46251303)) "Why not add this approach to postgres as a "JSONL3" type?" ([source](https://news.ycombinator.com/item?id=46260365))
- Edits single values in place (2 comments): "Lite^3 is a clever encoding for JSON data that is indexed as-encoded and is mutable in place." ([source](https://news.ycombinator.com/item?id=46251461)) "Lite³ supports replacing of individual values where ONLY the changed value needs updating." ([source](https://news.ycombinator.com/item?id=46254042))
- Schemaless, supports 64-bit ints (2 comments): "Supports 64 bit ints, raw byte datatype, zero-copy parsing, does not require schema" ([source](https://news.ycombinator.com/item?id=46133215)) "It's nice that it also works in a schemaless mode though." ([source](https://news.ycombinator.com/item?id=46508093))

## What people warn about

- Wire format not JSON-compatible (3 comments): "the headline makes it sound like the wire format is json compatible which is not the case" ([source](https://news.ycombinator.com/item?id=46323276)) "This is not JSON-compatible." ([source](https://news.ycombinator.com/item?id=46323531)) "JSON compatable is very different from convertable." ([source](https://news.ycombinator.com/item?id=46323730))
- Tied to hash function, key collisions (2 comments): "It's a bit unfortunate that the wire format is tied to a specific hash function." ([source](https://news.ycombinator.com/item?id=46323153)) "hash collision limitation for keys is the most questionable part of design" ([source](https://news.ycombinator.com/item?id=46323088))

## Alternatives hackers recommend

- [Protocol Buffers (protobuf)](https://hackerapproved.com/p/protocol-buffers.md): 77 recommend
- [Serde](https://hackerapproved.com/p/serde.md): 22 recommend
- [Cap'n Proto](https://hackerapproved.com/p/cap-n-proto.md): 20 recommend
- [Protobuf](https://hackerapproved.com/p/protobuf.md): 19 recommend
- [FlatBuffers](https://hackerapproved.com/p/flatbuffers.md): 16 recommend

## Cite as

Hacker Approved, "Lite³", https://hackerapproved.com/p/lite/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).