← Back to home
Comparison · Analytics

fellingdater vs markdown

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

Shared themes:r-package

fellingdater vs markdown: at a glance

Featurefellingdatermarkdown
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdendrochronology, crossdating, archaeology, ropenscimarkdown-rendering, maintenance-mode, succession, r-package
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 markdown?

A package that finished, declared itself done, and handed its core function to a successor.

The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.

Read the full markdown trajectory →

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

M
markdown
ANALYTICS
0.0

A package that finished, declared itself done, and handed its core function to a successor.

◆ Current state

The R markdown package spent 2023 adding real capability — fenced code block attributes, HTML widget rendering, compatibility shims for rmarkdown's document functions. Then 1.13 declared the package feature-complete and maintenance-only, naming litedown as where development continues. Version 2.0 completes that handover: mark(), the package's core function, is now a thin wrapper around litedown::mark(), and users are told to call litedown directly.

◆ Where it's heading

This is a controlled retirement rather than abandonment. The maintainer closed out the outstanding feature work first, announced the succession explicitly, and only then reduced the package to a compatibility surface. What remains is a stable shim for the installed base while new work happens in a package with a different name and scope.

◆ Prediction

Expect only CRAN-driven fixes here from now on, with any genuinely new rendering capability appearing in litedown instead. The entries state this policy directly, so the main open question is how long the wrapper is kept before deprecation warnings appear.

Alternatives to fellingdater and markdown

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

See all fellingdater alternatives → · See all markdown alternatives →

Recent activity from fellingdater and markdown

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

  1. 4mo agofellingdaterPolish for the crossdating plots and file reader
  2. 1y agofellingdaterAdds a full crossdating and tree-ring analysis toolkit
  3. 1y agofellingdaterUser-supplied sapwood data works across all functions
  4. 1y agofellingdaterFixes fd_report() with user-defined sapwood files
  5. 1y agomarkdownmark() becomes a thin wrapper around litedown::mark()
  6. 2y agomarkdownPackage declared feature-complete; work moves to litedown
  7. 2y agofellingdaterJOSS paper accepted; citation updated
  8. 2y agofellingdaterAdds a workflow vignette ahead of JOSS submission
  9. 2y agomarkdownAdds compatibility shims for rmarkdown's document functions
  10. 2y agomarkdownFixes verbatim code blocks with language attributes
  11. 2y agomarkdownFixes raw blocks broken by code-block attribute support
  12. 2y agomarkdownFenced code blocks gain attributes; HTML widgets render

Frequently asked questions

What is the difference between fellingdater and markdown?

Both compete on the same themes — r-package — within Analytics. fellingdater and markdown 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 markdown?

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

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