simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of atrrr and healthyR.data — release velocity, themes, recent moves, and the top alternatives to consider.
The R client for Bluesky adds a firehose and stops assuming Bluesky is the server
atrrr wraps the AT Protocol for R, covering posting, search, profiles, lists, direct messages and starter packs. The latest release adds an experimental firehose implementation and allows connecting to personal data servers other than Bluesky's — Eurosky is the example given. Earlier releases built out the posting surface: videos, multiple images, link preview cards, hashtags, and ggplot2 objects posted directly.
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.
atrrr wraps the AT Protocol for R, covering posting, search, profiles, lists, direct messages and starter packs. The latest release adds an experimental firehose implementation and allows connecting to personal data servers other than Bluesky's — Eurosky is the example given. Earlier releases built out the posting surface: videos, multiple images, link preview cards, hashtags, and ggplot2 objects posted directly.
Two years of work made atrrr a capable REST client for one network. This release starts undoing that second part. The firehose is a different access mode — a stream rather than a request — which is what researchers doing collection at scale need, and PDS-agnosticism means the package addresses the protocol rather than the company. The rest of the changelog is steadily maintenance-shaped: repeated httr2 compatibility work, endpoint changes tracked as they happen.
The firehose is labelled experimental, so the next release most likely stabilises it rather than opening another front — though the notes give no detail on what remains unfinished.
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 atrrr 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 atrrr 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. atrrr 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. atrrr 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 atrrr alternatives in Analytics are ranked by recent ship velocity. Browse the "atrrr alternatives" section above for the current picks, or visit /alternatives/atrrr 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.