r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of pkglite and poissonreg — release velocity, themes, recent moves, and the top alternatives to consider.
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.
poissonreg gave its models away to parsnip and kept the glue — now it just keeps glmnet honest.
poissonreg is a tidymodels extension that wires Poisson and zero-inflated count regression into the parsnip interface. Its defining event was giving up ownership: the model definition functions moved into parsnip itself, leaving this package as engine bindings and prediction plumbing. The current dev release is entirely correctness and hygiene work — glmnet predictions now default to mean counts rather than the linear predictor, and single-observation prediction works at last.
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.
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.
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.
poissonreg is a tidymodels extension that wires Poisson and zero-inflated count regression into the parsnip interface. Its defining event was giving up ownership: the model definition functions moved into parsnip itself, leaving this package as engine bindings and prediction plumbing. The current dev release is entirely correctness and hygiene work — glmnet predictions now default to mean counts rather than the linear predictor, and single-observation prediction works at last.
Release cadence has collapsed from yearly to a four-year gap between 1.0.1 and the current development version, and the content has shifted from features to deduplication against parsnip — copied helper functions replaced by the upstream originals, obsolete generic registrations removed, tests migrated to the shared extension-package pattern. This is what a stabilized tidymodels satellite looks like: the interface lives upstream, and the package's job is to not drift from it.
The dev version's accumulated fixes point to a CRAN release of 1.0.2 as the next move, with content limited to the glmnet prediction corrections rather than any new engine or model type.
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 pkglite or poissonreg.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all pkglite alternatives → · See all poissonreg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. pkglite and poissonreg 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. pkglite and poissonreg 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.
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.
Top poissonreg alternatives in Analytics are ranked by recent ship velocity. Browse the "poissonreg alternatives" section above for the current picks, or visit /alternatives/poissonreg for the full list with editorial commentary on each.