tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of cairo and protr — release velocity, themes, recent moves, and the top alternatives to consider.
Cairo finally catches R's graphics engine, all the way to GE API 16.
Cairo is the R device that renders plots through the cairo library, and until 1.7-0 it lagged R's own graphics engine by several API generations. That release closes the gap to GE API 16 (R 4.5.0), adding fill patterns, masks and groups. The releases before it were maintenance: a segfault shim for grid, a bashism removal in configure, and Windows font and build fixes.
protr's feature set is finished; the work now is surviving Bioconductor's churn.
protr generates numerical descriptors from protein sequences for machine learning, plus alignment-based similarity between sequences. The descriptor functions have been stable for years. Recent releases divide cleanly into two kinds: extending the similarity computations to work under memory constraints, and absorbing the Bioconductor split that moved pairwise alignment out of Biostrings into pwalign.
Cairo is the R device that renders plots through the cairo library, and until 1.7-0 it lagged R's own graphics engine by several API generations. That release closes the gap to GE API 16 (R 4.5.0), adding fill patterns, masks and groups. The releases before it were maintenance: a segfault shim for grid, a bashism removal in configure, and Windows font and build fixes.
The arc is catch-up, executed one API generation at a time. Glyph rendering arrived in 1.6-3, GE 15 stubs in 1.6-5 existed only to stop grid from segfaulting, and 1.7-0 delivers the real GE 13/14/16 feature set rather than placeholders. Alongside that, dropping the CAIROGD_VER C API and the mkdist step means the package now builds with plain R CMD build, which reads as deliberate reduction of maintenance overhead.
Expect the next releases to be corrective rather than additive: the entries show every API adoption here has been followed by a fix release, and patterns, masks and groups are a much larger surface than glyphs were.
protr generates numerical descriptors from protein sequences for machine learning, plus alignment-based similarity between sequences. The descriptor functions have been stable for years. Recent releases divide cleanly into two kinds: extending the similarity computations to work under memory constraints, and absorbing the Bioconductor split that moved pairwise alignment out of Biostrings into pwalign.
The similarity side is where the remaining engineering goes, and it follows a consistent pattern — whatever parSeqSim() gained, crossSetSim() eventually gets. Batching, verbose progress and a disk-backed variant all arrived for the single-set case first and were mirrored for the cross-set case in 1.7-1. That is a maintainer closing feature-parity gaps rather than opening new directions, and the two most recent releases contain no user-facing change at all.
Expect the next release to react to another Bioconductor or R CMD check change, which accounts for three of the last four. The similarity functions now have parity, so there is no obvious internal backlog left.
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 cairo or protr.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cairo and protr 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. cairo and protr 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 cairo alternatives in Analytics are ranked by recent ship velocity. Browse the "cairo alternatives" section above for the current picks, or visit /alternatives/cairo-r for the full list with editorial commentary on each.
Top protr alternatives in Analytics are ranked by recent ship velocity. Browse the "protr alternatives" section above for the current picks, or visit /alternatives/protr-r for the full list with editorial commentary on each.