Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of rlistings and tulpa — release velocity, themes, recent moves, and the top alternatives to consider.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
rlistings renders clinical-trial subject listings and paginates them for regulatory output, sitting alongside rtables on the shared formatters engine. The releases in this window are dominated by pagination correctness: repeated key columns across pages, splitting by a variable, ordered-factor handling, column gaps, and font metrics. Development is a large rotating contributor set inside the insightsengineering organisation.
The package is progressively delegating pagination to formatters rather than implementing it — paginate_listing() was refactored to call formatters' paginate_to_mpfs() directly, and truetype font support arrived through a new formatters API. That reduces duplicated logic but ties the package's page-break behaviour to a dependency it shares with rtables. Feature work beyond pagination is thin: better error messages for unsupported column classes, a cheatsheet.
Expect pagination fidelity to remain the focus, with changes arriving as formatters exposes more of its layout machinery rather than as rlistings-native features.
tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.
Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.
Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.
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 rlistings or tulpa.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
See all rlistings alternatives → · See all tulpa alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. 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. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top rlistings alternatives in Analytics are ranked by recent ship velocity. Browse the "rlistings alternatives" section above for the current picks, or visit /alternatives/rlistings for the full list with editorial commentary on each.
Top tulpa alternatives in Analytics are ranked by recent ship velocity. Browse the "tulpa alternatives" section above for the current picks, or visit /alternatives/tulpa for the full list with editorial commentary on each.