r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
nodbi vs typst-gather
A side-by-side editorial comparison of nodbi and typst-gather — release velocity, themes, recent moves, and the top alternatives to consider.
nodbi vs typst-gather: at a glance
What is nodbi?
One document API over six databases, and every release is spent absorbing their JSON engines' churn
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
What is typst-gather?
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.
nodbi vs typst-gather: editorial side-by-side
nodbi
0.0ANALYTICS
One document API over six databases, and every release is spent absorbing their JSON engines' churn
◆ Current state
nodbi presents a single document-store interface — docdb_create, docdb_query, docdb_update — over SQLite, DuckDB, PostgreSQL, MongoDB, CouchDB and Elasticsearch. The engineering reality behind that abstraction is that each backend's JSON support keeps moving, and the releases show it: jsonb_tree adopted as RSQLite 2.4.4 exposes it, json_tree reworked for DuckDB 1.3.0, then avoided entirely for DuckDB listfields because it was too slow. The 0.11.0 release in late 2024 is the one that changed the contract, making docdb_query() return columns of a single consistent type.
◆ Where it's heading
Two threads dominate. The first is performance, pursued backend by backend: fast direct NDJSON import moved from DuckDB-only to SQLite and PostgreSQL, query refactors chasing each DuckDB release, and the removal of expensive tree-walking where a cheaper path exists. The second is making results predictable — consistent column types, version checks on the database backend, clearer messages when a Postgres database does not exist yet or when column names contain the dots nodbi reserves for JSON paths.
◆ Prediction
Given that most recent releases are triggered by DuckDB and RSQLite version changes, the next one likely follows the same pattern — adopting a new JSON function or working around a slow one. The duplicate-_id handling added in 0.14.0 suggests NDJSON ingestion edge cases are the current active area.
typst-gather
0.0ANALYTICS
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
◆ Current state
typst-gather collects Typst packages into a local cache so documents build offline and hermetically. It was extracted from quarto-cli and reached CRAN-equivalent shape in three releases over a single day, then added an `analyze` subcommand that walks `@Preview` and `@Local` imports — following transitive dependencies of local packages — and prints structured JSON without downloading or copying anything.
◆ Where it's heading
The 0.2.0 restructuring is the tell: subcommands with backwards compatibility, config readable from stdin, and every diagnostic message moved to stderr so stdout carries nothing but JSON. Those are the conventions of a tool meant to be called by another program, not typed by a person. Given its origin inside Quarto's toolchain, the plausible consumer is a build system that needs to know a document's package requirements before deciding what to fetch.
◆ Prediction
The analyze path currently reports imports; the natural extension visible from here is acting on that report — lockfile output or verification that a cache satisfies a document's dependency set — though the entries do not commit to either.
Alternatives to nodbi and typst-gather
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either nodbi or typst-gather.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all nodbi alternatives → · See all typst-gather alternatives →
Recent activity from nodbi and typst-gather
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5mo agotypst-gatheranalyze subcommand reports the import graph as JSON ⚡
- 5mo agotypst-gatherWindows path escaping fix and README expansion
- 5mo agotypst-gatherSplit out of quarto-cli as a standalone package gatherer
- 8mo agonodbijsonb_tree adopted; $in string queries and duplicate _id handling fixed
- 1y agonodbiDuckDB version parsing and listfields fix
- 1y agonodbidocdb_query reworked for DuckDB 1.3.0
- 1y agonodbiNDJSON writing delegated to DuckDB's internal function
- 1y agonodbiQuery results get consistent column types; fast NDJSON import reaches SQLite and Postgres ⚡
- 1y agonodbiQuery and file-import speedups via newer DuckDB features
Frequently asked questions
What is the difference between nodbi and typst-gather?
They serve adjacent needs but don't currently overlap on shipped themes. nodbi and typst-gather are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is nodbi better than typst-gather?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nodbi and typst-gather are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to nodbi?
Top nodbi alternatives in Analytics are ranked by recent ship velocity. Browse the "nodbi alternatives" section above for the current picks, or visit /alternatives/nodbi for the full list with editorial commentary on each.
What are the best alternatives to typst-gather?
Top typst-gather alternatives in Analytics are ranked by recent ship velocity. Browse the "typst-gather alternatives" section above for the current picks, or visit /alternatives/typst-gather for the full list with editorial commentary on each.