r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of chattr and ymlthis — 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.
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
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.
ymlthis built R Markdown YAML front matter programmatically — a fluent `yml_*()` interface plus RStudio add-ins, so users did not have to hand-write metadata blocks whose valid fields were scattered across output-format documentation. Version 1.0.0 declares the package retired, with only CRAN-preserving changes to follow, and states the reason plainly: Quarto now provides good YAML support.
The retirement is the endpoint of a long drift. Between 2020 and 2022 every release was reactive — patching around a crayon update that mangled rendered YAML, tracking shiny 1.6, following roxygen2 7.0.0, fixing a typo in an add-in. No new capability has landed in six years, and the four-year gap before 1.0.0 had already answered the question the release note finally makes explicit.
Nothing further of substance is expected — the stated policy is changes only where CRAN requires them, so the next release, if any, will be a compatibility patch.
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 ymlthis.
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul took mocking back from webmockr and made it a property of the client itself
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all chattr alternatives → · See all ymlthis 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 ymlthis 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 ymlthis 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 ymlthis alternatives in Analytics are ranked by recent ship velocity. Browse the "ymlthis alternatives" section above for the current picks, or visit /alternatives/ymlthis for the full list with editorial commentary on each.