paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of TAF and xts — release velocity, themes, recent moves, and the top alternatives to consider.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
TAF is the R tooling behind the ICES Transparent Assessment Framework, which standardizes how fish stock assessments are laid out, sourced and rerun. The 4.3.0 release is the largest in years, adding roughly ten functions covering dependency installation and analysis, software version checks, directory inspection and README drafting. The package has carried zero non-base dependencies since 4.0.0, and the new work is careful not to break that.
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.
TAF is the R tooling behind the ICES Transparent Assessment Framework, which standardizes how fish stock assessments are laid out, sourced and rerun. The 4.3.0 release is the largest in years, adding roughly ten functions covering dependency installation and analysis, software version checks, directory inspection and README drafting. The package has carried zero non-base dependencies since 4.0.0, and the new work is careful not to break that.
The arc runs from analysis runner to project toolkit. Early 3.x releases built out the bootstrap and metadata machinery; 4.0.0 renamed the package and stripped every external dependency; 4.2.0 cleaned up vocabulary that confused users. 4.3.0 turns outward to the people running assessments — install.deps(), pdeps() and check.software() address reproducing someone else's environment, while draft.readme(), taf.example() and dir.tree() address understanding an unfamiliar project.
Expect the follow-up work to harden the new dependency functions rather than add more surface, since 4.3.1 arrived immediately to fix wide2long() compatibility with older R and that batch of ten functions has had little field exposure.
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 TAF or xts.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. TAF 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. TAF 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 TAF alternatives in Analytics are ranked by recent ship velocity. Browse the "TAF alternatives" section above for the current picks, or visit /alternatives/taf-r 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.