TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
A side-by-side editorial comparison of firatheme and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
A ggplot2 theme built around the Fira font family. It went quiet after the 2021 releases that made it pass R CMD check cleanly on all three platforms, then returned in December 2025 with a maintenance release solving a ggplot2 deprecation warning and cleaning up text alignment, followed six weeks later by a facet argument to theme_fira() that adds borders and a custom strip background so facet labels stay legible.
Rho's release machinery is now more rigorous than the product it ships.
Rho is an R IDE in open prerelease, and its public feed is almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
A ggplot2 theme built around the Fira font family. It went quiet after the 2021 releases that made it pass R CMD check cleanly on all three platforms, then returned in December 2025 with a maintenance release solving a ggplot2 deprecation warning and cleaning up text alignment, followed six weeks later by a facet argument to theme_fira() that adds borders and a custom strip background so facet labels stay legible.
The pattern of the revival is compatibility first, then the gap users actually hit. Faceting is the obvious hole in any hand-built theme — strip labels are where a theme that looks right on a single panel falls apart — and it arrived immediately after the deprecation cleanup, from a new contributor who has now made every recent change. Note the 0.2.4 release notes restate 0.2.3's contents rather than describing new work.
With faceting handled, further releases most likely track ggplot2 deprecations; the entries don't support a stronger claim than that.
Rho is an R IDE in open prerelease, and its public feed is almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
The project is building an agentic R IDE but publishing like a regulated release process: signed evidence, CONDITIONAL_GO records, checksums bound to exact commits, limitations named out loud rather than buried. dev.41 exists solely to rehearse the native updater across Windows and macOS, which is the last piece of distribution infrastructure between a dev train and something installable by people who won't build from source. Feature work and shipping work are advancing on separate tracks.
The updater acceptance target points at a 0.4.0 line that can update itself, so the next entry that matters is either dev.40's real publication or the first build not labelled evaluation-only. Whether Windows signing moves off the SignPath trial certificate is the open question these entries leave unanswered.
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 firatheme or Rho.
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
College football's open data client hit v2 — and now reports how many API calls you have left.
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all firatheme alternatives → · See all Rho alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Rho is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 firatheme alternatives in Analytics are ranked by recent ship velocity. Browse the "firatheme alternatives" section above for the current picks, or visit /alternatives/firatheme for the full list with editorial commentary on each.
Top Rho alternatives in Analytics are ranked by recent ship velocity. Browse the "Rho alternatives" section above for the current picks, or visit /alternatives/yulab-smu-rho for the full list with editorial commentary on each.