tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
r2rtf vs vcr
A side-by-side editorial comparison of r2rtf and vcr — release velocity, themes, recent moves, and the top alternatives to consider.
r2rtf vs vcr: at a glance
What is r2rtf?
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.
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.
r2rtf vs vcr: editorial side-by-side
r2rtf
0.0ANALYTICS
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
◆ Current state
r2rtf builds the RTF tables, listings and figures that go into clinical study reports, and its recent releases have been about widening who and what it can serve rather than changing how tables are composed. The 1.2.0 release added internationalization — a SimSun font path for Chinese characters plus hyphenation control — and 1.3.0 followed with write_docx() and write_html(), turning the LibreOffice conversion the package had documented into exported functions.
◆ Where it's heading
Two threads run through the window. One is output reach: RTF remains the composition target, but the artifacts that come out of it now include DOCX and HTML, and page numbering can be made table-relative across multi-page tables. The other is durability under a moving R and font stack — the ANSI/Unicode converter was rebuilt, the LaTeX mapping table generated from code rather than shipped as sysdata, unlist() usage fixed for R 4.5, and graphics-device leaks that produced stray Rplots.pdf closed off.
◆ Prediction
Having exported DOCX and HTML conversion, the likely next step is filling in what those formats lose relative to RTF — pagination and footnote fidelity are the obvious gaps. The i18n path currently covers Chinese only, so additional font families are the other plausible direction.
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 r2rtf 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 r2rtf or vcr.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
Recent activity from r2rtf and vcr
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agor2rtfDOCX and HTML output become exported functions
- 8mo agovcr2.0 removes the logging API and the exported R6 classes ⚡
- 11mo agor2rtfChinese character support arrives via an i18n font path ⚡
- 1y agor2rtfText colour fixed for figures encoded into RTF
- 1y agovcrMaintainer email address updated
- 1y agor2rtfFootnote handling fixed for R 4.5.0
- 1y agor2rtfUnicode converter rebuilt and mapping table made inspectable
- 2y agovcrAdds httr2 support alongside httr and crul ⚡
- 2y agor2rtfUTF-8 conversion fix and LibreOffice 7.6 support
- 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 r2rtf and vcr?
They serve adjacent needs but don't currently overlap on shipped themes. r2rtf 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 r2rtf better than vcr?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. r2rtf 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 r2rtf?
Top r2rtf alternatives in Analytics are ranked by recent ship velocity. Browse the "r2rtf alternatives" section above for the current picks, or visit /alternatives/r2rtf 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.