rjdqa
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
A side-by-side editorial comparison of rosm and xts — release velocity, themes, recent moves, and the top alternatives to consider.
rosm 0.3.0 silently deprecates its entire API and rebuilds on wk and curl
rosm downloads and stitches raster map tiles from OpenStreetMap and similar sources for use in R. After six years without a release, 0.3.0 deprecated the whole previous API, dropped the rgdal dependency, and introduced a replacement built on wk geometry and curl's multi-download interface. The follow-up 0.3.1 is documentation and CI work, plus test skips for Bing and Stamen URLs that no longer resolve.
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.
rosm downloads and stitches raster map tiles from OpenStreetMap and similar sources for use in R. After six years without a release, 0.3.0 deprecated the whole previous API, dropped the rgdal dependency, and introduced a replacement built on wk geometry and curl's multi-download interface. The follow-up 0.3.1 is documentation and CI work, plus test skips for Bing and Stamen URLs that no longer resolve.
The package is being brought back from dormancy on modern foundations rather than extended. rgdal's retirement forced the issue, and the maintainer used it to replace the download path with concurrent curl requests and to hand geometry handling to wk. What follows is consolidation: dead built-in tile sources are being tested around rather than replaced, which leaves the source registry as the obvious unfinished edge.
The dead Bing and Stamen endpoints are currently skipped rather than fixed, so the next release most likely prunes or re-points the built-in tile source list and continues retiring the silently deprecated functions.
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 rosm or xts.
rjdqa keeps refining one screen: the seasonal adjustment quality dashboard
epikit narrows to field-epidemiology helpers, handing proportions to a sibling package
SimInf 10.0 turns an epidemic simulator into a tool that fits models to real time series
A young package porting Stata's egen row-wise helpers to the tidyverse, one function per release
A statistician's personal toolbox, growing one plotting utility at a time
R/qtl is in pure custodial mode: every recent release answers a compiler, not a user
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. rosm 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. rosm 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 rosm alternatives in Analytics are ranked by recent ship velocity. Browse the "rosm alternatives" section above for the current picks, or visit /alternatives/rosm 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.