simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of healthyR.data and quanteda.textmodels — release velocity, themes, recent moves, and the top alternatives to consider.
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.
Split out of quanteda, then quiet - one new classifier since 2020.
quanteda.textmodels holds the scaling and classification models factored out of quanteda's main package. The visible history is thin: a logistic regression classifier and a native C++ rewrite of svmlin in late 2020, an SVM default change in early 2021, and after that only compatibility work. The most recent release fixes a namespace break caused by quanteda 4.1.0 dropping RcppArmadillo.
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.
quanteda.textmodels holds the scaling and classification models factored out of quanteda's main package. The visible history is thin: a logistic regression classifier and a native C++ rewrite of svmlin in late 2020, an SVM default change in early 2021, and after that only compatibility work. The most recent release fixes a namespace break caused by quanteda 4.1.0 dropping RcppArmadillo.
The package now moves when its parent or a dependency moves, not on its own schedule. Four of the six most recent releases exist to track changes in quanteda, Matrix, or CRAN policy. The modelling decisions that were made - defaulting textmodel_svm() to the L2-regularized L2-loss dual solver, reducing svmlin to a single algorithm - have not been revisited since.
The next release most likely follows another upstream change in quanteda or a Matrix and Rcpp dependency rather than adding a model.
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 healthyR.data or quanteda.textmodels.
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 healthyR.data alternatives → · See all quanteda.textmodels alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. healthyR.data and quanteda.textmodels 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. healthyR.data and quanteda.textmodels 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 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.
Top quanteda.textmodels alternatives in Analytics are ranked by recent ship velocity. Browse the "quanteda.textmodels alternatives" section above for the current picks, or visit /alternatives/quanteda-textmodels for the full list with editorial commentary on each.