r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of gMCPLite and poissonreg — release velocity, themes, recent moves, and the top alternatives to consider.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
gMCPLite is a fork of gMCP with the Java dependency removed and `hGraph()` ported over from gsDesign, giving R users graphical multiple comparison procedures and their visualisation without a JVM. Since that fork, no release has added a statistical capability. The visible history is compatibility work: ggplot2 3.5.0 argument naming, a cairo device for Unicode in examples, testthat 3.3.0 snapshot requirements, and a selective port of an upstream confidence-interval fix.
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.
gMCPLite is a fork of gMCP with the Java dependency removed and `hGraph()` ported over from gsDesign, giving R users graphical multiple comparison procedures and their visualisation without a JVM. Since that fork, no release has added a statistical capability. The visible history is compatibility work: ggplot2 3.5.0 argument naming, a cairo device for Unicode in examples, testthat 3.3.0 snapshot requirements, and a selective port of an upstream confidence-interval fix.
This is a package with a fixed job. The maintainers track two moving targets — the upstream gMCP it forked from, and the R graphics and testing stack underneath it — and pull across only what is needed. The addition of vdiffr visual regression tests for `hGraph()` is the most substantive recent change and fits the same posture: the plots are the deliverable, so pin them against accidental drift rather than redesign them.
Expect the pattern to continue — compatibility releases driven by ggplot2, testthat and pkgdown changes, with any statistical content arriving only as a selective port from upstream gMCP.
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 gMCPLite 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 gMCPLite alternatives → · See all poissonreg alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-language, maintenance — within Analytics. gMCPLite 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. gMCPLite 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 gMCPLite alternatives in Analytics are ranked by recent ship velocity. Browse the "gMCPLite alternatives" section above for the current picks, or visit /alternatives/gmcplite 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.