edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of kwb.db and rrum — release velocity, themes, recent moves, and the top alternatives to consider.
A water-research lab's ODBC helper, still fighting Windows database drivers a decade in.
kwb.db is internal tooling from Kompetenzzentrum Wasser Berlin that wraps ODBC access to MS Access and similar databases for the lab's R workflows. Its functionality covers schema inspection, relation reading and database dumps, with a long-standing preoccupation with the 32-bit versus 64-bit driver split on Windows. The most recent release pins a newer RODBC to fix Windows installation.
Six years past its API cleanup, rrum ships only what the compiler demands.
rrum estimates the reduced Reparameterized Unified Model via a Gibbs sampler in Rcpp/Armadillo, with simulation delegated to its sibling package simcdm. The user-facing API has been settled since 2019, when the entry point was renamed and simulation was moved out. Releases since then have been build and CRAN compliance work.
kwb.db is internal tooling from Kompetenzzentrum Wasser Berlin that wraps ODBC access to MS Access and similar databases for the lab's R workflows. Its functionality covers schema inspection, relation reading and database dumps, with a long-standing preoccupation with the 32-bit versus 64-bit driver split on Windows. The most recent release pins a newer RODBC to fix Windows installation.
The visible history is dominated by driver plumbing rather than features. Early versions added a bridge for calling 32-bit ODBC drivers from a 64-bit R session, then reversed course once 64-bit drivers shipped with MS Office, preferring RODBC directly and falling back only when needed. Later work exposed more of the internals — dumpDatabase, SQL builders, then schema and relation readers — turning a connection helper into something closer to a metadata extractor. The 2025 release is pure survival, and its note candidly records that Ubuntu and macOS installs still fail in CI.
Expect the next release to respond to another RODBC or driver breakage rather than to add functionality, given that installation has been the binding problem across the last several releases.
rrum estimates the reduced Reparameterized Unified Model via a Gibbs sampler in Rcpp/Armadillo, with simulation delegated to its sibling package simcdm. The user-facing API has been settled since 2019, when the entry point was renamed and simulation was moved out. Releases since then have been build and CRAN compliance work.
The arc runs from an API-breaking consolidation in 2019, through a 2023 release fixing C++ deprecations and adding a pkgdown site, to a 2025 maintenance release that raises dependency floors and swaps a deprecated Armadillo conversion call. Each release is triggered by something outside the package — R-devel, CRAN check notes, an Armadillo deprecation — rather than by modeling work. The 2025 release arrived the same morning as a near-identical one for edina, marking it as a maintainer-wide sweep across the lab's packages.
The next release will most likely be another externally forced compatibility fix, since three consecutive releases have been reactions to toolchain deprecations rather than to user requests.
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 kwb.db or rrum.
A grammar for experimental design that learned to compose designs and track its own provenance.
A Swiss clinical-trial data reader that surfaces once every couple of years to clear check notes.
Brazil's flight-data package keeps working around what ANAC publishes and when.
A star-schema modelling package grew a query language, a deployment path, and then a map layer.
PACTA's loan-book matcher opened up to sector taxonomies other than its own.
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. kwb.db and rrum 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. kwb.db and rrum 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.
Top kwb.db alternatives in Analytics are ranked by recent ship velocity. Browse the "kwb.db alternatives" section above for the current picks, or visit /alternatives/kwb-db for the full list with editorial commentary on each.
Top rrum alternatives in Analytics are ranked by recent ship velocity. Browse the "rrum alternatives" section above for the current picks, or visit /alternatives/rrum for the full list with editorial commentary on each.