gcube
gcube's recent releases are all packaging metadata, not simulation code
A side-by-side editorial comparison of fillpattern and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
Pattern fills for ggplot2, hardened against the ways users write sizes
fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.
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.
fillpattern provides pattern fills — stripes, bricks, dots — for ggplot2 and base R graphics, aimed at figures that must stay legible in greyscale or to colour-blind readers. The 1.0.3 release is mostly defensive: size modifier strings ending in a colon no longer swap width for height, modify_size() reports invalid units instead of crashing and understands in, inches and cm, and a background colour bug in scale_fill_pattern() is fixed. The minimum R version rises to 4.2.0 for recent graphics engine features.
Development is slow and entirely reactive to how the string-based size interface fails. The pattern across releases is the same: a user hits an edge — very small fill areas in 1.0.2, malformed unit strings in 1.0.3 — and the fix is either a graceful fallback or a clearer error. Leaning on R's newer graphics engine rather than reimplementing pattern rendering keeps the package small at the cost of raising its version floor.
Expect further releases to stay in the same register: parsing and validation fixes for the size and unit interface, with the pattern set itself unlikely to change.
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 fillpattern or Rho.
gcube's recent releases are all packaging metadata, not simulation code
The R port of Quinlan's Cubist gets reproducibility fixes, not new modelling
ggstats keeps widening what a coefficient or Likert plot can be
ecodive rebuilt itself into a broad diversity-metric library, breaking as it went
State-space data simulation for R, filled in one function at a time
rollama turns a local-LLM wrapper into an instrument for reproducible annotation
See all fillpattern 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 fillpattern alternatives in Analytics are ranked by recent ship velocity. Browse the "fillpattern alternatives" section above for the current picks, or visit /alternatives/fillpattern 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.