tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of riem and Tplyr — release velocity, themes, recent moves, and the top alternatives to consider.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
Tplyr made clinical summary tables explain where every number came from.
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
riem pulls observations from the Iowa Environmental Mesonet's weather-station network. Its release history is two threads: successive rewrites of the HTTP and test-mocking stack, and a gradual tightening of function arguments that culminated in 1.0.0 removing convenient-but-dangerous defaults. Contributions come partly from IEM's own maintainer.
The HTTP thread has moved through httr to httr2, and mocking from vcr to httptest2 — following the broader rOpenSci HTTP-stack reorganisation rather than any need of its own. The API thread runs the other way: 1.0.0 removed defaults for date_start and station and flipped latlon to FALSE, trading convenience for callers being explicit about what they request. New arguments in the same release widened what a query can ask for.
With the API stabilised at 1.0.0 and the HTTP stack settled on httr2, the next release is more likely to expose additional IEM query parameters than to change plumbing again.
Tplyr builds clinical summary tables through a layered grammar — count, descriptive statistics, and shift layers assembled onto a table object. The 1.0.0 release added a traceability metadata framework that lets a user ask which source rows produced any given cell, and later releases extended it to cases the first pass missed. The package is maintained by Atorus within the pharmaverse ecosystem.
Post-1.0 work has been about completing the metadata story and filling gaps in layer composition rather than adding table types — metadata for missing subjects, add_anti_join(), missing-subject rows, data limiting, and fixes to nested count layers where an inner value appears under several outer groups. Releases cluster tightly after a major version, then go quiet, and the window ends with a patch issued days after the release it corrects.
Further releases will most likely continue closing traceability and nested-layer edge cases rather than introducing new layer types, following the pattern of both post-1.0 feature releases.
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 riem or Tplyr.
A tables-listings-graphs package that reached CRAN and then went quiet.
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. riem and Tplyr 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. riem and Tplyr 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 riem alternatives in Analytics are ranked by recent ship velocity. Browse the "riem alternatives" section above for the current picks, or visit /alternatives/riem for the full list with editorial commentary on each.
Top Tplyr alternatives in Analytics are ranked by recent ship velocity. Browse the "Tplyr alternatives" section above for the current picks, or visit /alternatives/tplyr for the full list with editorial commentary on each.