tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of riem and tinkr — 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.
Markdown round-tripping through XML, where every release is another thing it learned not to mangle.
tinkr parses Markdown into XML, lets callers manipulate it with XPath, and writes it back out — the yarn R6 class is the whole interface. Its development is defined by a single hard problem: surviving the round trip without corrupting syntax the XML representation does not natively model. Maintenance is shared between two active contributors and release cadence is roughly annual.
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.
tinkr parses Markdown into XML, lets callers manipulate it with XPath, and writes it back out — the yarn R6 class is the whole interface. Its development is defined by a single hard problem: surviving the round trip without corrupting syntax the XML representation does not natively model. Maintenance is shared between two active contributors and release cadence is roughly annual.
Each release extends the set of constructs that get protected across the round trip — curly braces, escaped brackets, inline math, dollar signs used as currency, French-style dollars, fenced divs, frontmatter. The 0.3.0 notes also add get_protected(), append_md(), and prepend_md(), which is the first sign of building a manipulation API on top of the protection machinery rather than only widening it.
Expect the protection list to keep growing toward full Quarto syntax coverage, which the first release named as the long-term goal and which fenced divs and frontmatter both move toward.
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 tinkr.
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, ropensci — within Analytics. riem and tinkr 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 tinkr 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 tinkr alternatives in Analytics are ranked by recent ship velocity. Browse the "tinkr alternatives" section above for the current picks, or visit /alternatives/tinkr for the full list with editorial commentary on each.