datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
Comparison · Analytics
markdown vs vcr
A side-by-side editorial comparison of markdown and vcr — release velocity, themes, recent moves, and the top alternatives to consider.
markdown vs vcr: at a glance
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.
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.
markdown vs vcr: editorial side-by-side
markdown
0.0ANALYTICS
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.
vcr
0.0ANALYTICS
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 markdown 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 markdown or vcr.
maplegend
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
lang
R help pages translated on demand by whichever LLM you point it at.
mapsf
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
fabletools
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all markdown alternatives → · See all vcr alternatives →
Recent activity from markdown and vcr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agovcr2.0 removes the logging API and the exported R6 classes ⚡
- 1y agomarkdownmark() becomes a thin wrapper around litedown::mark()
- 1y agovcrMaintainer email address updated
- 2y agovcrAdds httr2 support alongside httr and crul ⚡
- 2y agomarkdownPackage declared feature-complete; work moves to litedown ⚡
- 2y agomarkdownAdds compatibility shims for rmarkdown's document functions
- 2y agomarkdownFixes verbatim code blocks with language attributes
- 2y agomarkdownFixes raw blocks broken by code-block attribute support
- 2y agomarkdownFenced code blocks gain attributes; HTML widgets render
- 3y agovcrDrops compilation; test setup moves back to helper files
- 3y agovcrFixes request matching with escaped characters
- 5y agovcrvcr_test_path() finds the package root correctly
Frequently asked questions
What is the difference between markdown and vcr?
They serve adjacent needs but don't currently overlap on shipped themes. markdown 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 markdown better than vcr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. markdown 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 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.
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.