Tplyr
Tplyr made clinical summary tables explain where every number came from.
Comparison · Analytics
riem vs tidytlg
A side-by-side editorial comparison of riem and tidytlg — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
riem vs tidytlg: at a glance
What is riem?
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.
What is tidytlg?
A tables-listings-graphs package that reached CRAN and then went quiet.
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
riem vs tidytlg: editorial side-by-side
riem
0.0ANALYTICS
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
tidytlg
0.0ANALYTICS
A tables-listings-graphs package that reached CRAN and then went quiet.
◆ Current state
tidytlg generates clinical tables, listings, and graphs from tidyverse-style pipelines, maintained under the pharmaverse organisation. All four releases in the window are from a single eight-month stretch in 2023, and their content is CRAN preparation, a logging-dependency swap, and multi-file support. Release notes are merge lists rather than described changes.
◆ Where it's heading
The visible arc is getting onto CRAN and staying installable — vignette corrections per CRAN comments, a badge, a check fix, and replacing the timber logging package with logrx. The one functional addition is multiple-file support. There has been no release since October 2023, so on this evidence the package is stable or dormant rather than actively developing.
◆ Prediction
The entries give no signal about planned work; with nothing shipped in roughly two years, the more likely next event is a maintenance release triggered by a dependency or CRAN check than a feature.
Alternatives to riem and tidytlg
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 tidytlg.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
ijtiff
A TIFF reader for scientific imaging that spent its recent releases shedding weight and fixing memory bugs.
See all riem alternatives → · See all tidytlg alternatives →
Recent activity from riem and tidytlg
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agoriem1.0.0 removes defaults and adds query arguments
- 1y agoriemDrops the last vcr usage in favour of httptest2
- 2y agoriemTimezone and timestamp-parsing fixes
- 2y agotidytlgSwaps the timber logger for logrx
- 3y agotidytlgMultiple-file support and table-binding fixes
- 3y agotidytlgVignette update per CRAN comments
- 3y agotidytlgFirst CRAN release
- 4y agoriemMoves to httr2 and httptest2
- 4y agoriemSwitches to newer IEM metadata web services
- 9y agoriemReduces dependencies to tibble alone
Frequently asked questions
What is the difference between riem and tidytlg?
Both compete on the same themes — r-package — within Analytics. riem and tidytlg 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.
Is riem better than tidytlg?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. riem and tidytlg 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.
What are the best alternatives to riem?
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.
What are the best alternatives to tidytlg?
Top tidytlg alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytlg alternatives" section above for the current picks, or visit /alternatives/tidytlg for the full list with editorial commentary on each.