tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of lightr and riem — release velocity, themes, recent moves, and the top alternatives to consider.
Reorganised its parsers by vendor, then opened the parser slot to users.
lightr reads spectrometry files from the proprietary formats that instrument vendors ship, and its recent releases have been about the structure of that parser collection rather than adding one more format. Version 2.0.0 renamed every low-level parser from lr_parse_<extension>() to lr_parse_<brand>_<extension>(), a breaking change made specifically so two vendors can share a file extension without colliding, and restored binary parsing for Avantes AvaSoft 8.4 using vendor-supplied format documentation. Version 2.1.0 follows through by exposing a parser argument on the high-level functions.
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.
lightr reads spectrometry files from the proprietary formats that instrument vendors ship, and its recent releases have been about the structure of that parser collection rather than adding one more format. Version 2.0.0 renamed every low-level parser from lr_parse_<extension>() to lr_parse_<brand>_<extension>(), a breaking change made specifically so two vendors can share a file extension without colliding, and restored binary parsing for Avantes AvaSoft 8.4 using vendor-supplied format documentation. Version 2.1.0 follows through by exposing a parser argument on the high-level functions.
The package is moving from a fixed set of formats it knows about to a dispatch system users can extend. The brand-qualified naming and the parser argument are two halves of the same design: name parsers unambiguously, then let callers select or supply one. Alongside that runs steady attention to metadata fidelity — measurement timestamps, checksum verification against tampering, and timezone handling that survived upstream tzdata removing legacy codes.
Expect additional vendor parsers to arrive under the new brand-qualified scheme, and the custom-parser path to absorb formats the maintainers do not want to support directly. The entries do not name specific instruments planned next.
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.
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 lightr or riem.
A tables-listings-graphs package that reached CRAN and then went quiet.
Tplyr made clinical summary tables explain where every number came from.
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.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. lightr and riem 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. lightr and riem 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 lightr alternatives in Analytics are ranked by recent ship velocity. Browse the "lightr alternatives" section above for the current picks, or visit /alternatives/lightr for the full list with editorial commentary on each.
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.