r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
nanonext vs pkglite
A side-by-side editorial comparison of nanonext and pkglite — release velocity, themes, recent moves, and the top alternatives to consider.
nanonext vs pkglite: 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 pkglite?
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.
nanonext vs pkglite: 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.
pkglite
0.0ANALYTICS
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
◆ Current state
pkglite packs an R package into a single plain-text file and unpacks it again, the mechanism pharmaceutical submissions use to move source through systems that accept text but not archives. The API settled at 0.2.0 with file specification templates, `merge()` and `prune()`. Every release since has improved the same thing: the dictionary that decides whether a file is text or binary, most recently rebuilt from the file extensions found across 21,369 CRAN packages.
◆ Where it's heading
The failure mode this package cares about is silent — misclassify a binary file as text and the round trip corrupts it, misclassify text as binary and it bloats or drops. So the work is empirical rather than architectural: mine real packages for what extensions actually appear, then widen coverage where specific ecosystems break the pattern. Stan interfaces via rstan brought `src/Makevars` and `src/Makefile` handling; machine learning frameworks brought their own binary formats. Dependencies have gone the other way, with cli removed and replaced by internal equivalents.
◆ Prediction
Expect the next substantive release to widen file specification coverage again for whatever package family the maintainers find breaking the default discovery, since that has been the content of every non-maintenance release for four years.
Alternatives to nanonext and pkglite
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 pkglite.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
dendroNetwork
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all nanonext alternatives → · See all pkglite alternatives →
Recent activity from nanonext and pkglite
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
- 5mo agopkgliteMaintainer email and CI workflow updates
- 1y agopkgliteHandles Stan-interfacing packages and ML binary formats
- 1y agopkgliteExtension dictionary rebuilt from 21,369 CRAN packages
- 2y agopkgliteTest helpers moved to helper.R
- 3y agopkgliteMore file types recognised; cli dependency dropped
- 5y agopkgliteFile collections gain merge, prune, and a tests template
Frequently asked questions
What is the difference between nanonext and pkglite?
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 pkglite?
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 pkglite?
Top pkglite alternatives in Analytics are ranked by recent ship velocity. Browse the "pkglite alternatives" section above for the current picks, or visit /alternatives/pkglite for the full list with editorial commentary on each.