tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of quantities and xts — release velocity, themes, recent moves, and the top alternatives to consider.
The glue package that makes R carry units and uncertainty through the same calculation.
quantities combines the units and errors packages into one class so values keep both their measurement units and their uncertainty through arithmetic, subsetting and data frame operations. Recent releases have been narrow: fixes to the covariance and correlation implementations, and performance work on the data.frame methods. Most of the release traffic is coordination with its two parent packages.
xts is finished software, and its releases now track R's C API more than user requests.
xts is the time-series class underpinning much of R's financial stack, and it behaves like infrastructure: the visible releases are bug fixes, plotting repairs and conformance work. A recurring thread is removing calls R no longer considers public — SET_TYPEOF in 0.14.0 and 0.14.1, then ATTRIB() and SET_ATTRIB() in 0.14.2. Feature additions are rare and small, the last cluster being open-ended time-of-day subsetting and na.fill performance in 0.13.0.
quantities combines the units and errors packages into one class so values keep both their measurement units and their uncertainty through arithmetic, subsetting and data frame operations. Recent releases have been narrow: fixes to the covariance and correlation implementations, and performance work on the data.frame methods. Most of the release traffic is coordination with its two parent packages.
The design settled with 0.2.0, which made uncertainty unit-aware and added correlation and covariance support for quantities objects. Since then the package behaves like the integration layer it is — releasing when units, errors, dplyr or ggplot2 shift underneath it rather than on its own schedule. Several releases consist only of test repairs against upstream changes.
Expect the next release to follow a units or errors change rather than introduce new behaviour of its own.
xts is the time-series class underpinning much of R's financial stack, and it behaves like infrastructure: the visible releases are bug fixes, plotting repairs and conformance work. A recurring thread is removing calls R no longer considers public — SET_TYPEOF in 0.14.0 and 0.14.1, then ATTRIB() and SET_ATTRIB() in 0.14.2. Feature additions are rare and small, the last cluster being open-ended time-of-day subsetting and na.fill performance in 0.13.0.
Two forces drive releases. R core keeps narrowing its public C API, and xts keeps rewriting internals to stay inside it; separately, ggplot-era changes elsewhere in the ecosystem surface plotting bugs that get fixed one report at a time. Nearly every entry credits an outside reporter, which is what maintenance of a dependency this widely used looks like.
Further C API conformance work is the safest expectation, since two consecutive releases have each removed a different non-API entry point and R has continued tightening that boundary.
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 quantities or xts.
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.
A fish diet package whose release history is really a record of surviving rfishbase.
See all quantities alternatives → · See all xts alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. quantities and xts 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. quantities and xts 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 quantities alternatives in Analytics are ranked by recent ship velocity. Browse the "quantities alternatives" section above for the current picks, or visit /alternatives/quantities for the full list with editorial commentary on each.
Top xts alternatives in Analytics are ranked by recent ship velocity. Browse the "xts alternatives" section above for the current picks, or visit /alternatives/xts-r for the full list with editorial commentary on each.