r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of gMCPLite and mlr3spatial — 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.
Raster prediction in mlr3 finally returns class probabilities, not just hard labels.
mlr3spatial connects mlr3 learners to raster and vector spatial data, handling chunked prediction over large rasters through DataBackendRaster. Development is slow and fix-heavy: most releases in the last two years were compatibility work against mlr3 and paradox rather than new capability. 0.7.0 is the exception.
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.
mlr3spatial connects mlr3 learners to raster and vector spatial data, handling chunked prediction over large rasters through DataBackendRaster. Development is slow and fix-heavy: most releases in the last two years were compatibility work against mlr3 and paradox rather than new capability. 0.7.0 is the exception.
The package tracks the mlr3 core rather than leading it — 0.5.0 and 0.6.1 exist to absorb upstream changes in paradox and mlr3. Against that background, 0.7.0 adding probability predictions to predict_spatial() is the first genuine capability increase in a while, arriving alongside two DataBackendRaster fixes for multi-band sources and similarly-named layers. Cadence is roughly one release per year.
Given the pattern, the next release is more likely to be compatibility work against a new mlr3 or terra version than another feature; further raster-backend edge cases around layer naming are the visible loose end.
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 mlr3spatial.
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 mlr3spatial alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gMCPLite and mlr3spatial 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 mlr3spatial 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 mlr3spatial alternatives in Analytics are ranked by recent ship velocity. Browse the "mlr3spatial alternatives" section above for the current picks, or visit /alternatives/mlr3spatial for the full list with editorial commentary on each.