edibble
A grammar for experimental design that learned to compose designs and track its own provenance.
A side-by-side editorial comparison of hubVis and r2dii.match — release velocity, themes, recent moves, and the top alternatives to consider.
The hubverse plotting layer spends its releases absorbing upstream churn, not adding charts.
hubVis is the visualization component of the hubverse stack, centred on plot_step_ahead_model_output() for static and interactive forecast plots. Since the stable 0.1.0 in late 2024 it has shipped three patch releases, every one of them a single referenced issue fix. The plotting surface itself has not grown.
PACTA's loan-book matcher opened up to sector taxonomies other than its own.
r2dii.match links entries in a bank's loan book to companies in the asset-based company data, combining an optional exact join on a shared ID with fuzzy name matching. Since 0.3.0 the sector classification used for that matching is an explicit argument rather than a fixed default, letting institutions bring their own taxonomy. Recent releases have been documentation and messaging work under a new maintainer.
hubVis is the visualization component of the hubverse stack, centred on plot_step_ahead_model_output() for static and interactive forecast plots. Since the stable 0.1.0 in late 2024 it has shipped three patch releases, every one of them a single referenced issue fix. The plotting surface itself has not grown.
The pattern across all four releases is narrow and reactive: a legend construction fix, a palette assignment fix, and most recently a compatibility change for ggplot2 4.0.0 written to keep working with earlier versions too. Two of the three fixes concern colour and legend handling, which suggests palette assignment is the fragile part of the codebase. As a thin layer over ggplot2 inside a larger stack, the package's release triggers come from below it rather than from its own roadmap.
Expect continued single-issue patches driven by upstream ggplot2 changes and by whatever the sibling hubverse packages emit, rather than new plot types.
r2dii.match links entries in a bank's loan book to companies in the asset-based company data, combining an optional exact join on a shared ID with fuzzy name matching. Since 0.3.0 the sector classification used for that matching is an explicit argument rather than a fixed default, letting institutions bring their own taxonomy. Recent releases have been documentation and messaging work under a new maintainer.
The package has spent its releases removing assumptions. The ald to abcd migration completed the move to the current data vocabulary, join_id gave users a way to bypass fuzzy matching where they already hold a reliable identifier, and sector_classification opened the taxonomy itself. Each of these hands control back to the user for a decision the package previously made. Activity has since shifted to hygiene — a data_dictionary describing every column, cli-based messaging, documentation edits — and the maintainer handover in 0.4.0 fits that pattern. The data_dictionary landed here two days after the same addition to r2dii.plot, so this is a family-wide convention rather than one package's idea.
With the API opened up and a new maintainer settling in, expect continued alignment work across the r2dii family rather than changes to the matching algorithm itself.
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 hubVis or r2dii.match.
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.
A water-research lab's ODBC helper, still fighting Windows database drivers a decade in.
PACTA's climate-alignment charting layer split prep from plotting, then settled into stable.
See all hubVis alternatives → · See all r2dii.match alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. hubVis and r2dii.match 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. hubVis and r2dii.match 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 hubVis alternatives in Analytics are ranked by recent ship velocity. Browse the "hubVis alternatives" section above for the current picks, or visit /alternatives/hubvis for the full list with editorial commentary on each.
Top r2dii.match alternatives in Analytics are ranked by recent ship velocity. Browse the "r2dii.match alternatives" section above for the current picks, or visit /alternatives/r2dii-match for the full list with editorial commentary on each.