simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of fastglm and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
A fast GLM solver stops being one function and becomes a count-model family
fastglm ran C++ IRLS for standard generalized linear models for six years with almost no releases. In May 2026 it added three top-level model types — negative binomial with jointly estimated dispersion, hurdle, and zero-inflated — each with the entire fitting driver in C++ rather than an R loop around a C++ kernel. The following release generalised Firth bias reduction to every standard family across dense, sparse and streaming backends.
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.
fastglm ran C++ IRLS for standard generalized linear models for six years with almost no releases. In May 2026 it added three top-level model types — negative binomial with jointly estimated dispersion, hurdle, and zero-inflated — each with the entire fitting driver in C++ rather than an R loop around a C++ kernel. The following release generalised Firth bias reduction to every standard family across dense, sparse and streaming backends.
The package changed what it is. Through 0.0.3 it was a drop-in replacement for glm() competing on speed; from 0.1.0 it targets the models people leave base R for — MASS::glm.nb, pscl::hurdle, pscl::zeroinfl — and reimplements their full estimation loops natively. The 0.1.1 follow-up is consolidation on that new surface: Firth generalised past binomial logit, SQUAREM acceleration on the zero-inflation EM driver, and a run of clamping guards and initialization fixes on the families most prone to overflow.
The numerical-stability work in 0.1.1 clusters on Tweedie and the inverse and sqrt link families, which suggests those paths are the newest and least exercised — expect further correctness fixes there before new model types.
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 fastglm 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 fastglm 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. fastglm 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. fastglm 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 fastglm alternatives in Analytics are ranked by recent ship velocity. Browse the "fastglm alternatives" section above for the current picks, or visit /alternatives/fastglm 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.