r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of BaseSet and gMCPLite — release velocity, themes, recent moves, and the top alternatives to consider.
A tidy interface for set algebra that reached 1.0 and has been quiet since.
BaseSet gives R a tidy-style TidySet object for set operations, including fuzzy sets. The 1.0.0 release in early 2025 rounded out the object's ergonomics — subsetting by sets and elements, dimnames() and names(), an all argument on the name and count helpers — and dropped magrittr by raising the R dependency to 4.1. There has been no release in the eighteen months since.
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.
BaseSet gives R a tidy-style TidySet object for set operations, including fuzzy sets. The 1.0.0 release in early 2025 rounded out the object's ergonomics — subsetting by sets and elements, dimnames() and names(), an all argument on the name and count helpers — and dropped magrittr by raising the R dependency to 4.1. There has been no release in the eighteen months since.
Development followed a clear arc from correctness to usability: early releases were CRAN and packaging compliance, 0.9.0 built out extractors and setters so TidySets behave like native R objects, and 1.0.0 finished the naming and subsetting surface. Reaching 1.0 reads as a deliberate stopping point rather than a staging post, and the cadence since supports that.
The package looks feature-complete and maintenance-only; the most likely next release is a CRAN compliance or dependency fix rather than new set operations.
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.
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 BaseSet or gMCPLite.
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 BaseSet alternatives → · See all gMCPLite alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. BaseSet and gMCPLite 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. BaseSet and gMCPLite 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 BaseSet alternatives in Analytics are ranked by recent ship velocity. Browse the "BaseSet alternatives" section above for the current picks, or visit /alternatives/baseset for the full list with editorial commentary on each.
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.