r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
A side-by-side editorial comparison of dwctaxon and ymlthis — release velocity, themes, recent moves, and the top alternatives to consider.
A Darwin Core validator that went quiet for two years, then surfaced only to raise its R floor
dwctaxon edits and validates taxonomic data held in Darwin Core format, enforcing the referential rules that make a taxonomic database internally consistent. Its last real functional change was 2.0.3 in December 2023, which loosened an over-strict uniqueness requirement in column matching. The most recent entry is a development build two years later that does nothing but set a minimum R version and bump Roxygen.
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.
dwctaxon edits and validates taxonomic data held in Darwin Core format, enforcing the referential rules that make a taxonomic database internally consistent. Its last real functional change was 2.0.3 in December 2023, which loosened an over-strict uniqueness requirement in column matching. The most recent entry is a development build two years later that does nothing but set a minimum R version and bump Roxygen.
The visible arc is a package converging on correctness rather than growing. The 2.0.3 change is the most consequential: matching a reference column no longer demands that every value in it be unique, only that the matched values be — which is what makes dct_fill_col() usable on real taxonomic tables where scientificName legitimately repeats. Around it sits compliance work: an internet-connection and URL check added purely to satisfy CRAN policy, and examples reworked to restore user settings and skip deliberate errors.
The 2.0.3.9001 development stamp with an R >= 4.2.0 requirement suggests a 2.0.4 release is being prepared, most likely as maintenance rather than new validation rules. The two-year gap makes any stronger claim unsupported by the feed.
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 dwctaxon 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
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
See all dwctaxon 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. dwctaxon 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. dwctaxon 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 dwctaxon alternatives in Analytics are ranked by recent ship velocity. Browse the "dwctaxon alternatives" section above for the current picks, or visit /alternatives/dwctaxon 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.