tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
nanonext vs r2rtf
A side-by-side editorial comparison of nanonext and r2rtf — release velocity, themes, recent moves, and the top alternatives to consider.
nanonext vs r2rtf: at a glance
What is nanonext?
nanonext keeps shrinking its build requirements while adding messaging primitives.
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
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.
nanonext vs r2rtf: editorial side-by-side
nanonext
2.5ANALYTICS
nanonext keeps shrinking its build requirements while adding messaging primitives.
◆ Current state
The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.
◆ Where it's heading
Two directions run in parallel. One is making the package installable anywhere — the build-time cmake dependency is gone, so compiling bundled NNG and Mbed TLS needs only a C compiler, and WebAssembly targets are supported. The other is raising the ceiling on what can be built on top: device_aio() for message forwarding, an HTTP and WebSocket server with a content map, and stream buffer control. Bug fixes in recent releases concentrate on memory safety in the bundled C sources.
◆ Prediction
Given the pace and the tight coupling declared in each release, expect the next version to track a mirai requirement and continue hardening the HTTP server paths that the last two releases have been leaking memory in.
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.
Alternatives to nanonext and r2rtf
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 nanonext or r2rtf.
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.
See all nanonext alternatives → · See all r2rtf alternatives →
Recent activity from nanonext and r2rtf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10d agonanonextMemory leaks and a TLS use-after-free fixed in the HTTP server
- 1mo agonanonextEvent-loop integration for HTTP and WebSocket callbacks
- 1mo agonanonextZero-copy message forwarding, and cmake dropped from the build ⚡
- 2mo agonanonextBuilds against pthread-enabled WebAssembly targets
- 3mo agonanonextSerialized sends drop a copy and halve peak memory
- 4mo agonanonextBlocking HTTP server mode and stream buffer sizing
- 7mo agor2rtfDOCX and HTML output become exported functions
- 11mo agor2rtfChinese character support arrives via an i18n font path ⚡
- 1y agor2rtfText colour fixed for figures encoded into RTF
- 1y agor2rtfFootnote handling fixed for R 4.5.0
- 1y agor2rtfUnicode converter rebuilt and mapping table made inspectable
- 2y agor2rtfUTF-8 conversion fix and LibreOffice 7.6 support
Frequently asked questions
What is the difference between nanonext and r2rtf?
They serve adjacent needs but don't currently overlap on shipped themes. nanonext is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 nanonext better than r2rtf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. nanonext is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 nanonext?
Top nanonext alternatives in Analytics are ranked by recent ship velocity. Browse the "nanonext alternatives" section above for the current picks, or visit /alternatives/nanonext for the full list with editorial commentary on each.
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.