simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of hoopr and rtrek — release velocity, themes, recent moves, and the top alternatives to consider.
hoopR rebuilds its HTTP layer on httr2 to stop segfaulting on modern systems
hoopR is the sportsdataverse R package for basketball data, wrapping ESPN, NBA Stats, NBA G-League, NCAA and KenPom behind a single set of loaders. Version 3.0.0 replaces httr with httr2 across every one of those backends, drops httr from Imports, and routes all calls through shared internal retry and response helpers. The change is breaking, and it exists because the old stack segfaulted against libcurl 8.x and curl 7.0.0.
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
hoopR is the sportsdataverse R package for basketball data, wrapping ESPN, NBA Stats, NBA G-League, NCAA and KenPom behind a single set of loaders. Version 3.0.0 replaces httr with httr2 across every one of those backends, drops httr from Imports, and routes all calls through shared internal retry and response helpers. The change is breaking, and it exists because the old stack segfaulted against libcurl 8.x and curl 7.0.0.
The package's history is two distinct eras. Through 2021-2023 it grew by endpoint accretion — ESPN stat functions, G-League coverage, the NBA live and boxscore V3 families, on-court players in play-by-play — expanding what could be pulled. The recent work is consolidation instead: one HTTP pipeline, one messaging library, data served from the shared sportsdataverse-data releases rather than per-package repositories. The centre of gravity has moved from adding endpoints to making the plumbing survive its dependencies.
With the HTTP layer unified behind shared helpers, expect the sibling sportsdataverse packages to follow the same httr2 migration, and hoopR's own next releases to resume endpoint work now that requests run through one pipeline.
rtrek bundles Star Trek datasets — book series, timelines, episode transcripts, species and homeworlds, map tile sets — and layers live retrieval on top through memory_alpha() and memory_beta() plus their ma_* and mb_* helpers. Recent releases are almost entirely repairs to that retrieval layer as the source wikis change their page structure.
The package's centre of gravity shifted once, at 0.2.0, from shipping static data to querying Memory Alpha and Memory Beta at runtime. Everything since has been the maintenance bill for that decision: HTML update fixes, parser improvements, portal retrieval bugs. Note that version numbers on this feed do not track time — 0.2.5 is stamped a year before 0.1.0, and three tags were backfilled within four minutes in November 2020 — so neither rank nor version ordering here indicates release sequence.
Expect the next release to fix retrieval against another Memory Alpha layout change, which is what the last four have done. The entries give no indication of new datasets or functions in progress.
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 hoopr or rtrek.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — api-client — within Analytics. hoopr and rtrek 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. hoopr and rtrek 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 hoopr alternatives in Analytics are ranked by recent ship velocity. Browse the "hoopr alternatives" section above for the current picks, or visit /alternatives/hoopr for the full list with editorial commentary on each.
Top rtrek alternatives in Analytics are ranked by recent ship velocity. Browse the "rtrek alternatives" section above for the current picks, or visit /alternatives/rtrek for the full list with editorial commentary on each.