hist-prototype VS tql

I have 2 projects that I'm looking to eventually adapt into a database backend that's API compatible with RocksDB (with enhancements!). The first of which is a Extendible Hashing Implementation in Rust (it was my first attempt at Rust, so it's kinda messy): https://github.com/chiefnoah/MehDB

It achieves very promising performance for u64 sized types (which will eventually be an offset into a log).

The other is a similar concept using modified B+Trees that have subtrees for all writes to a record: https://github.com/chiefnoah/hist-prototype

This one is implemented in Python for fast iteration, as I realized I wasn't happy with how fast I could iterate with Rust. This one is, IMO, a more complete approach towards full historical query-capable systems. I'm slowly chipping away at it, though I haven't had progress lately. I spend no real money to host them, just the code, though I'm certain I've shortened the life of my NVMe drives due to writing and rewriting large files for testing.

Can we do projects that we think will stay at $0 but we still hope might gain traction?

OSS: typed-graphql-builder https://typed-graphql-builder.spion.dev/ is a TypeScript based graphql query builder.

It was inspired by tql (https://tql.dev/) but generates a much smaller client and has full, automatic type inference for query variables used in input objects.