HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
beached
daw_json_link
C++2019–2024
beached / daw_json_link

daw_json_link

Fast, convenient JSON serialization and parsing in C++

4Distinct people
10Mentions
0Explicit recommenders
514GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fast, convenient JSON serialization and parsing in C++

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 11:34:28 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year10 dated mentions

Observed mentions: 2019-08-16 15:04:32 UTC to 2024-11-14 07:32:54 UTC.

0123452019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC312
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC505

What Hacker News says

3 sources

Show HN: DAW JSON Link

I just released v3 of DAW JSON Link https://github.com/beached/daw_json_link, a C++ JSON library, that I am the author of. It's a C++ JSON library that prioritizes concrete data structures. It is fast, GB/s, and competitive with other libraries out there like simdjson. A brief list of things it supports are: * declaratively map json objects to C++ data structures * allows allocators to be provided and passes it to allocator aware types * can parse via a non-owning json_value that allows JSON Path like indices along with iteration of sub members * types to provide iteration over json arrays and use in C++ algorithms * JSON Lines/NDJSON support * The parser does not allocate at all, that is up to the resulting data structures, if needed. The memory usage is very minimal * Variants/Sum types are a priority and most express
Read the rest
ions of them in JSON have easy mappings with a fallback to code if needed * JSON Schema output from mappings * Custom number types are supported(e.g Boost Multi-precision/GNU MP) * Serialization to most things is supported out of the box with the ability to easily add a new way. This includes, pointer, output iterators, span like types, strings/vectors/containers of byte like types, FILE ... An accompanying project https://github.com/beached/daw_json_link_describe that allows using Boost.Describe reflection like mappings with JSON Link * Lots of example code in tests folder and cookbook like documentation in the docs folder to see it in use. All the examples in documentation are part of the test suite too * Optionally allows for comments( # line comments and C-style // and /* /) Allows for trailing comma * constexpr
3 points · Open discussion
Not Rust, but for C++ I have found a lot of memory and CPU perf can be realized by knowing what is being parsed into and using that. Most JSON parsing optimize on array/object/number/bool/null and not things like unsigned integer being much faster to parse than a float(floating point hit cpu bottlenecks around 1GB/s). Additionally, allowing for compile time options to further optimize is much easier. Essentially most JSON parsers are type erased. https://github.com/beached/daw_json_link So this correlates with some of the findings the post has. One optimization that should show great promise is that if one knows that they have an array of some types like numbers/unsigned int/strings, that can greatly simplify and allow for SIMD'ification of it.
In Deserializing JSON Fast (2020)

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.