simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of gratia and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
The tidy front-end for GAMs, now stable enough that upstream ggplot2 sets its release calendar.
gratia wraps mgcv-fitted generalized additive models in tidy data frames and ggplot2 graphics — smooth_estimates(), fitted_values(), derivatives(), draw() and appraise() cover evaluation, prediction and diagnostics. The API reached its intended shape at 0.9.0, when every generated column was renamed to a dot-prefixed form, and 0.10.0 added conditional_values() for covariate-conditional prediction plots.
From a bundled hospital dataset to a live CMS API client.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
gratia wraps mgcv-fitted generalized additive models in tidy data frames and ggplot2 graphics — smooth_estimates(), fitted_values(), derivatives(), draw() and appraise() cover evaluation, prediction and diagnostics. The API reached its intended shape at 0.9.0, when every generated column was renamed to a dot-prefixed form, and 0.10.0 added conditional_values() for covariate-conditional prediction plots.
The package has moved through a long rewrite cycle and out the other side. Successive releases replaced evaluate_smooth() with smooth_estimates(), rebuilt draw() on top of it, then renamed the entire output vocabulary to avoid colliding with user variables. That work is finished; 0.11.1 is driven almost entirely by ggplot2 4.0.0 compatibility, with new mgcv family support for quantile residuals riding along. Development now tracks upstream breakage rather than internal redesign.
Expect the next releases to continue absorbing ggplot2 4.x and mgcv changes, with incremental family coverage in quantile_residuals() as the visible new work. The entries give no signal on which mgcv families come next.
healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.
The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.
With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.
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 gratia or healthyR.data.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
A nycflights13 generator whose recent work is all about the data being right.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
See all gratia alternatives → · See all healthyR.data alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. gratia and healthyR.data 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. gratia and healthyR.data 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 gratia alternatives in Analytics are ranked by recent ship velocity. Browse the "gratia alternatives" section above for the current picks, or visit /alternatives/gratia for the full list with editorial commentary on each.
Top healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data for the full list with editorial commentary on each.