qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of cairo and fossilsim — 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.
A fossil-record simulator that quietly grew a trait-evolution engine.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
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.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
The arc runs from sampling mechanics toward simulating what the organisms actually were. Version 2.2.0 taught the package to handle occurrence data for occurrence birth-death models; 2.3.0 then added trait simulation under Mk, BM and OU, which is a different kind of output than fossil ages. Since then the work has been maintenance and keeping the FossilSimShiny GUI in step, suggesting the authors consider the current model set feature-complete.
The pairing of the 2.3.3 release with a FossilSimShiny version bump points to the GUI, not the library, as where the next visible work lands. The entries do not show enough activity to predict a specific new model family.
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 fossilsim.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all cairo alternatives → · See all fossilsim alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. cairo and fossilsim 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 fossilsim 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 fossilsim alternatives in Analytics are ranked by recent ship velocity. Browse the "fossilsim alternatives" section above for the current picks, or visit /alternatives/fossilsim-r for the full list with editorial commentary on each.