G0g0xA52A2A·May 21, 2023Submission
Deco – Delimiter Collision Free Format
2 points · Open discussionEnhex
Deco
C++2017–2023
Enhex / Deco
Deco
Delimiter Collision Free Format
5Distinct people
6Mentions
0Explicit recommenders
85GitHub stars
What to know before exploring
What it is
Delimiter Collision Free Format
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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM 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 year6 dated mentions
Observed mentions: 2017-12-27 18:06:19 UTC to 2023-05-21 16:17:43 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 2 | 0 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 1 | 0 |
What Hacker News says
6 sourcesIf you like JSON that much, obviously you haven't yet seen
https://github.com/Enhex/Deco
In Atom was archived todayi was annoyed by the verbosity of XML when using it for config files at my workplace so i tried to design maximally human readable & writable text file format, which turned out to be extremely concise and fast:
https://github.com/Enhex/Deco
after trying at least dozen C++ GUI libs and none of them being good enough (license, limited portability, limited customability,...) i started making my own one which is OpenGL based, got automatic layouting, separation of concerns of layout/style/logic, permissive license, and provides building blocks to make your own widgets.
https://github.com/Enhex/GUI
In Ask HN: What are some tools / libraries you built yourself?I actually think this is a great idea. There are a few immediate questions I have though.
1) how does one define a key with a ": "
2) as others said, significant whitespace, specifically trailing, seems to lead problems with keys that have nested key/val, array, multiline string.
3) the github repo associated with the parser has an isue that questions how to verify if the file was truncated.
I think Deco: https://github.com/Enhex/Deco better solves the problem the OP has. It is provably delimiter collision free, unlike this (see my point 1 Unless I'm mistaken).
In NestedText, a nice alternative to JSON, YAML, TOMLDeco: Delimiter Collision Free Format
3 points · Open discussionDeco – Delimiter Collision Free Format (2,000% Faster Than JSON)
3 points · Open discussion