rjd3highfreq
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
Comparison · Analytics
gtsummary vs units
A side-by-side editorial comparison of gtsummary and units — release velocity, themes, recent moves, and the top alternatives to consider.
gtsummary vs units: at a glance
What is gtsummary?
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
What is units?
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
gtsummary vs units: editorial side-by-side
gtsummary
0.0ANALYTICS
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
◆ Current state
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
◆ Where it's heading
The ARD work is the through-line. Table IDs exist so gather_ard() can return a named list; hierarchical tables gained per-level sorting and targeted filtering; ARD inputs are pre-processed so sorting applies to non-standard shapes. The package is becoming a structured-results engine that happens to render tables, rather than a renderer alone. Alongside that, 2.2.0 restored data pre-processing that 2.0 had removed after the reduced functionality hurt users — a maintainer willing to reverse a major-version decision.
◆ Prediction
Expect the hierarchical and ARD functions, introduced as a preview without a full deprecation cycle, to keep stabilizing toward a settled API rather than new table types appearing.
units
0.0ANALYTICS
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
◆ Current state
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
◆ Where it's heading
The long 0.8-x run was accretion — ggplot2 scales absorbed from ggforce, ud_convert(), matrix methods, steady performance work — while known parsing defects stayed in place. The 1.0 release finally traded backwards compatibility for correct parsing, and 1.0-1's pointer-wrapping and exception-propagation work suggests the C++ glue is being hardened behind it. Fixes cluster at the udunits2 boundary, which remains the main source of surprises.
◆ Prediction
Expect continued patch releases against udunits2 quirks and the new tokenizer's fallout rather than new surface area, with the ggplot2 integration and conversion helpers already in place.
Alternatives to gtsummary and units
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 gtsummary or units.
audubon
audubon's release feed is almost entirely Renovate bumping the JavaScript toolchain behind its Japanese text splitter.
affiner
affiner is quietly turning a grid transformation helper into a small computational geometry library.
ageproR
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
r-ledger
ledger adds a Rust toolchain fallback, so beancount imports work whether or not the Python tooling is installed.
gridpattern
gridpattern keeps widening its catalogue, and the newest patterns finally use the device's own line rendering.
See all gtsummary alternatives → · See all units alternatives →
Recent activity from gtsummary and units
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agogtsummaryTheme elements no longer evaluated by default
- 5mo agounitsMemory-leak and udunits2 parsing fixes after 1.0
- 8mo agogtsummaryARD strata functions and finer theme control
- 10mo agounitsNew tokenizer parses compound units correctly ⚡
- 11mo agogtsummaryPer-level hierarchical sorting and labeled stacking
- 1y agogtsummaryTable splitting, ID labeling, and add_difference_row
- 1y agogtsummaryData pre-processing restored after the 2.0 removal
- 1y agounitsCopy semantics fix in ud_convert(); C++17 for old R
- 1y agounitscbind/rbind methods, ud_convert() and broad fixes
- 1y agogtsummarytbl_merge gains explicit merge columns
- 1y agounitsSilences a CRAN compiler warning
- 2y agounitsRestores simplify=FALSE for identical units
Frequently asked questions
What is the difference between gtsummary and units?
They serve adjacent needs but don't currently overlap on shipped themes. gtsummary and units 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.
Is gtsummary better than units?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gtsummary and units 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.
What are the best alternatives to gtsummary?
Top gtsummary alternatives in Analytics are ranked by recent ship velocity. Browse the "gtsummary alternatives" section above for the current picks, or visit /alternatives/gtsummary-r for the full list with editorial commentary on each.
What are the best alternatives to units?
Top units alternatives in Analytics are ranked by recent ship velocity. Browse the "units alternatives" section above for the current picks, or visit /alternatives/units-r for the full list with editorial commentary on each.