← Back to home
Comparison · Analytics

fellingdater vs vcr

A side-by-side editorial comparison of fellingdater and vcr — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:ropensci

fellingdater vs vcr: at a glance

Featurefellingdatervcr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdendrochronology, crossdating, archaeology, ropenscitesting, http-mocking, breaking-change, api-cleanup
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is fellingdater?

Went from estimating felling dates to doing the crossdating that produces them.

fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.

Read the full fellingdater trajectory →

What is vcr?

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

Read the full vcr trajectory →

fellingdater vs vcr: editorial side-by-side

F
fellingdater
ANALYTICS
0.0

Went from estimating felling dates to doing the crossdating that produces them.

◆ Current state

fellingdater estimates when a tree was felled from sapwood measurements, the core inference in dendrochronological dating of timber. Version 1.0.0 passed rOpenSci review with that scope, and the 2024 releases were mostly about the accompanying JOSS paper and user-supplied sapwood datasets. Version 1.2.0 changed the package's remit substantially, adding an entire trs_* family for tree-ring series handling: crossdating with multiple statistical measures, the Hollstein and Baillie-Pilcher t-value transformations, parallel variation percentages, synthetic series generation, and dated-series plotting.

◆ Where it's heading

The package has expanded backwards along the workflow. It began at the last step — given dated series, estimate the felling date — and 1.2.0 added the step before it, establishing those dates by crossdating in the first place. Version 1.2.1 is early polish on that new surface: axis control, non-syntactic column names, encoding safety in read_fh(). The direction is a single package covering the chain from raw ring widths to a felling-date estimate.

◆ Prediction

Expect the trs_* family to keep accumulating polish and additional crossdating statistics, since it is barely a year old and 1.2.1 was already fixing its plotting and top_n behaviour. Whether the two halves of the package get unified into one workflow interface is the open question the entries do not answer.

V
vcr
ANALYTICS
0.0

Added the HTTP client everyone moved to, then deleted a decade of its own public surface.

◆ Current state

vcr records HTTP interactions to disk so R package tests can replay them without network access. Two releases define its current state. Version 1.6.0 added httr2 support alongside the existing httr and crul backends, following the R ecosystem's migration to httr2. Version 2.0 then removed a large amount of accumulated public surface — the logging functions, vcr_last_error(), the exported R6 classes including RequestHandler, Request, VcrResponse and HTTPInteractionList, and several configuration options that had stopped working or could not be implemented correctly.

◆ Where it's heading

The package is consolidating after years of additive growth. The 2.0 removals are almost all things that were exported without needing to be, or options that promised behaviour the implementation could not guarantee — check_cassette_names() was deprecated precisely because it cannot be made correct. Cassette maintenance is being simplified too, with re_record_interval now the single mechanism for expiring recordings.

◆ Prediction

Expect the post-2.0 releases to be about migration support and fallout from the removed API, since the breaking list is long enough that reverse dependencies will surface problems. Async support for httr2 stays blocked until req_perform_parallel gains a mocking hook, which the entries note is upstream work.

Alternatives to fellingdater and vcr

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 fellingdater or vcr.

See all fellingdater alternatives → · See all vcr alternatives →

Recent activity from fellingdater and vcr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agofellingdaterPolish for the crossdating plots and file reader
  2. 8mo agovcr2.0 removes the logging API and the exported R6 classes
  3. 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit
  4. 1y agofellingdaterUser-supplied sapwood data works across all functions
  5. 1y agofellingdaterFixes fd_report() with user-defined sapwood files
  6. 1y agovcrMaintainer email address updated
  7. 2y agovcrAdds httr2 support alongside httr and crul
  8. 2y agofellingdaterJOSS paper accepted; citation updated
  9. 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
  10. 3y agovcrDrops compilation; test setup moves back to helper files
  11. 3y agovcrFixes request matching with escaped characters
  12. 5y agovcrvcr_test_path() finds the package root correctly

Frequently asked questions

What is the difference between fellingdater and vcr?

Both compete on the same themes — ropensci — within Analytics. fellingdater and vcr 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.

Is fellingdater better than vcr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. fellingdater and vcr 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.

What are the best alternatives to fellingdater?

Top fellingdater alternatives in Analytics are ranked by recent ship velocity. Browse the "fellingdater alternatives" section above for the current picks, or visit /alternatives/fellingdater for the full list with editorial commentary on each.

What are the best alternatives to vcr?

Top vcr alternatives in Analytics are ranked by recent ship velocity. Browse the "vcr alternatives" section above for the current picks, or visit /alternatives/vcr for the full list with editorial commentary on each.