qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of cairo and constants — 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.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.
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.
constants exposes the CODATA recommended values of the physical constants to R, as a data frame plus symbol lists that carry units, uncertainties, or both. The package reached 1.0.0 on the 2018 CODATA release and has shipped once since, purely to track a units package update. Its surface is small and its release cadence is bound to CODATA, which revises every few years.
The direction set at 1.0.0 was to stop being a curated convenience wrapper and become a mechanical mirror of NIST. Hand-crafted symbol names were replaced with NIST's own ASCII symbols, categories adopted NIST's, and uncertainty switched from relative to absolute — all framed by the maintainer as necessary to make future CODATA updates routine. On top of that the package gained a correlation matrix and optional integration with the quantities package, moving it from a lookup table toward something that can propagate uncertainty.
Having rebuilt the symbol table specifically so CODATA revisions become mechanical, the next substantive release most likely tracks a new CODATA dataset rather than adding API. The experimental correlated-value support, disabled by default at 1.0.0, is the one part these entries flag as unfinished.
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 constants.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
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.
A fossil-record simulator that quietly grew a trait-evolution engine.
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 constants 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 constants 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 constants 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 constants alternatives in Analytics are ranked by recent ship velocity. Browse the "constants alternatives" section above for the current picks, or visit /alternatives/constants-r for the full list with editorial commentary on each.