InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now. Learn more β
Librdx Alternatives
Similar projects and alternatives to librdx
-
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
-
zig
General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
-
txtai
π‘ All-in-one open-source AI framework for semantic search, LLM orchestration and language model workflows
-
-
-
-
InfluxDB
InfluxDB β Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
mockoon
Mockoon is the easiest and quickest way to run mock APIs locally. No remote deployment, no account required, open source.
-
learn-anything
Make interlinked notes in private (E2E encrypted), share parts of it to global network of topics with deep AI integration
-
-
-
-
-
-
salsa
A generic framework for on-demand, incrementalized computation. Inspired by adapton, glimmer, and rustc's query system.
-
-
-
-
MKS-DLC32
MKS DLC32 motherboard kit, which is an offline engraving master control kit developed for desktop engraving machines. The hardware is equipped with a 32-bit high-speed ESP32 module, integrated WIFI function, and directly drives a 3.5-inch touch color screen; it can realize fast engraving and WEB web pages. Control, mobile phone APP control and other functions.
-
kviklet
Pull Request-like Review/Approval flow for database queries. For compliant but smooth Engineering access to production.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
librdx discussion
librdx reviews and mentions
- Escher's Art and Computer Science
- People Keep Inventing Prolly Trees
-
I Write Type Safe Generic Data Structures in C
*
1 point by gritzko 3 minutes ago | parent | context | edit | delete | on: I Write Type Safe Generic Data Structures in C
Hi. I object.
The trick#0 you mention is how I made an entire C dialect. Here is a generic binary heap, for example https://github.com/gritzko/librdx/blob/master/abc/HEAPx.h The syntax is a bit heavyweight, but a huge huge advantage is: you get regular C structs in the end, very plain, very predictable, very optimizable. Compiler would eat them like donuts.
In the other cases, it is void* and runtime memory sizing and you have to define macros anyway.
-
Homomorphically Encrypting CRDTs
The first CRDTs have been remarkably impractical, e.g. WOOT. These days, state-of-the-art CRDT databases are not much different from your regular LSM performance-wise. For example, RDX CRDTs are all implemented by a merge-sort-like algorithm, pure O(N). Metadata overheads have been tamed in most implementations.
[1]: https://github.com/gritzko/librdx
-
Flattening ASTs (and Other Compiler Data Structures)
I work on a C dialect where everything is flattened. JSON and other trees in particular. Binary heaps are flat, merge sort and iterator heaps are absolutely great, can build LSM databases with that. Stacks, circular buffers, hash maps, etc, all flat. Templated output (PHP like) is done by a flat data structure.
https://github.com/gritzko/librdx/blob/master/abc/B.md
-
Blogs Rot. Wikis Wait
And even in solo projects, I have been in situations when I had to check my own docs to understand what's going on.
As a result, my project is effectively also a wiki:
https://replicated.wiki/abc/
https://github.com/gritzko/librdx/tree/master/abc
The idea is to put motivational and explanatory text into the parallel wiki, while all the API docs stay in the code the normal way. These are seriously different things.
The next step to unit tests all the code docs. Or, the other way around, to document tests to make them joy to read. That is the only way to solve doc rot.
Overall, I am trying to get as close to Literate programming as practically possible:
- Nested ${templating} engine in 150 lines of C
-
Show HN: A portable hash map in C
I recently coded a linear-probing hash map in C and I highly recommend you to use fuzz tests. These evolve naturally from unit tests: next step table unit tests, next step property test, next step fuzzing, all steps are incremental, hence easy.
Having a fuzz test was in-va-lu-ab-le. I caught several bugs right there. The delete function was particularly tricky.
I ended up with two fuzz tests as my hash table has a key feature: convergence. Having same contents, it would have exactly same bits in the buffer. In other words, it is independent of the insertion/deletion order. For this, I added another fuzz test. I would add a third one if I would realize there is an important invariant I did not fuzz test. That is not much work, but so much useful!
https://github.com/gritzko/librdx/blob/master/abc/fuzz/HASH....
-
Why I love Rust for tokenising and parsing
I love love love ragel.
Won't the code here:
https://github.com/gritzko/librdx/blob/master/JSON.lex
accept "[" as valid json?
delimiter = OpenObject | CloseObject | OpenArray | CloseArray | Comma | Colon;
- ABC buffers: as simple as possible, but not simpler
-
A note from our sponsor - InfluxDB
www.influxdata.com | 18 Jul 2025
Stats
gritzko/librdx is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of librdx is C.