← Back to home
Comparison · Analytics

fellingdater vs Plotly

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

fellingdater vs Plotly: at a glance

FeaturefellingdaterPlotly
SectorAnalyticsAnalytics
Velocity score0.06.3
Sparks · 30d01
Top themesdendrochronology, crossdating, archaeology, ropensciai-app-building, plotly-cloud, metered-billing, custom-domains
Last editorial update4d ago7h 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 Plotly?

Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.

Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.

Read the full Plotly trajectory →

fellingdater vs Plotly: 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.

P
Plotly
ANALYTICS
6.3

Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.

◆ Current state

Plotly ships on two tracks. Plotly Studio, the desktop AI app-builder, releases every one to two weeks and has spent v0.0.80 through v0.0.86 on credential handling, reasoning transparency, personalization and now the reliability of the agent session engine itself. Plotly Cloud is the louder track: since late May it has added viewer-seat pricing, domain verification, per-app compute modes with credit-metered billing, and customer-owned domains with managed TLS.

◆ Where it's heading

The Cloud releases are assembling the standard pieces of a hosting business in order — identity first (domain verification, explicitly framed as the step before SSO), then billing (viewer seats, then metered compute credits), and now production-grade serving (custom domains, automatic certificate renewal). Studio is being hardened as the authoring front end that feeds it: Universal Deployment pushed beyond Dash apps, credentials saved once and reused, a Winget channel to widen Windows installs, and in v0.0.86 a rebuilt session engine plus automatic retries so agent runs survive expired tokens. The two tracks converge on one funnel — author in Studio, deploy to Cloud, pay by compute consumed.

◆ Prediction

The Domain Verification entry names SSO as the next step and places it in the Enterprise tier, so single sign-on is the most likely Cloud release next. Studio should hold its one-to-two-week cadence, with the newly added app thumbnails pointing toward more work on browsing and organizing generated apps.

Alternatives to fellingdater and Plotly

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 Plotly.

See all fellingdater alternatives → · See all Plotly alternatives →

Recent activity from fellingdater and Plotly

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

  1. 14d agoPlotlyCustom Domains in Plotly Cloud
  2. 24d agoPlotlyPlotly Studio v0.0.85: Breadcrumbs & minor bug fixes
  3. 1mo agoPlotlyPlotly Studio v0.0.84: Faster AI, Saved Credentials, and Winget Support
  4. 1mo agoPlotlyCompute Modes and App Sizing in Plotly Cloud
  5. 1mo agoPlotlyPlotly Studio 0.0.83: Dash Update and macOS Fixes
  6. 2mo agoPlotlyPlotly Studio v0.0.82: Override for credential redaction, stability fixes
  7. 4mo agofellingdaterPolish for the crossdating plots and file reader
  8. 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit
  9. 1y agofellingdaterUser-supplied sapwood data works across all functions
  10. 1y agofellingdaterFixes fd_report() with user-defined sapwood files
  11. 2y agofellingdaterJOSS paper accepted; citation updated
  12. 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission

Frequently asked questions

What is the difference between fellingdater and Plotly?

They serve adjacent needs but don't currently overlap on shipped themes. Plotly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is fellingdater better than Plotly?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Plotly is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 editorial sparks in the last 30 days against 0. 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 Plotly?

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