tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
A side-by-side editorial comparison of chattr and daiquiri — release velocity, themes, recent moves, and the top alternatives to consider.
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.
A data-quality report generator that finished its API rewrite and has been coasting on small features since.
daiquiri turns a raw clinical or administrative dataset into an HTML report of time-series data-quality plots, driven by a field-type specification the user writes. The public API settled in 2022 after a wholesale rename for rOpenSci acceptance, and releases since then have added specification conveniences rather than new report content. The 1.2.0 release is the first in nearly two years.
chattr puts a large language model inside the RStudio IDE, either through a Shiny app or directly at the console. As of 0.3.0 it no longer talks to any model provider itself: all integration goes through ellmer, and the hand-written OpenAI, Databricks and LlamaGPT backends were removed. The package's supported model list is now whatever ellmer supports, and the Shiny app streams responses through ellmer rather than managing a background process.
The first two releases show why that happened. Each provider brought its own error formats, token discovery and response handling, and 0.2.0 is largely a list of per-provider repairs — OpenAI error parsing, Copilot token discovery and model defaults, a new Databricks foundation model backend. Maintaining that surface scales linearly with the number of providers, and the pivot to ellmer trades it for a single dependency. The cost shows up immediately in 0.3.1, which exists solely to absorb a change in ellmer's token object.
Expect chattr's releases to now track ellmer's, as 0.3.1 already does, with the package's own work concentrating on the IDE experience rather than model connectivity. New provider support will arrive without a chattr release at all.
daiquiri turns a raw clinical or administrative dataset into an HTML report of time-series data-quality plots, driven by a field-type specification the user writes. The public API settled in 2022 after a wholesale rename for rOpenSci acceptance, and releases since then have added specification conveniences rather than new report content. The 1.2.0 release is the first in nearly two years.
Development has shifted from restructuring the interface to lowering the cost of using it — field_types_advanced() lets users name only the columns they care about and default the rest, which is the kind of change that matters when a dataset has hundreds of fields. Plot rendering is getting incremental attention (heatmap scaling) rather than new visualisation types. Cadence is roughly annual.
Expect the next release to continue trimming specification boilerplate for wide datasets rather than adding report sections; the entries give no indication of a new plot type or output format 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 chattr or daiquiri.
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.
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all chattr alternatives → · See all daiquiri alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. chattr and daiquiri 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. chattr and daiquiri 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 chattr alternatives in Analytics are ranked by recent ship velocity. Browse the "chattr alternatives" section above for the current picks, or visit /alternatives/chattr for the full list with editorial commentary on each.
Top daiquiri alternatives in Analytics are ranked by recent ship velocity. Browse the "daiquiri alternatives" section above for the current picks, or visit /alternatives/daiquiri for the full list with editorial commentary on each.