May want to sprinkle in "hinting" on the nature of operations done the
database, which could allow LMDB to deal with those far more efficiently
(for example, a read-only transaction can just be done as soon as the
JSON itself is parsed out, as we don't really need the former anymore!)
Currently doing a test run on another project of mine to find out how
stable it is.
Next up(more long-termed): Faster JSON parsing than just plaintext!
Start of my work to get out LMDB support. I want to make it optional, as
some environments just can't use LMDB(due to mapped RAM limits, or
places where mmap is unavailable (a rather cursed platform!)).
Next up: Start separating Db to allow multiple subimplementations
instead of being expressly for nested-dir JSON ops.
