tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
daiquiri vs textreuse
A side-by-side editorial comparison of daiquiri and textreuse — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
daiquiri vs textreuse: at a glance
What is daiquiri?
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.
What is textreuse?
A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.
textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.
daiquiri vs textreuse: editorial side-by-side
daiquiri
0.0ANALYTICS
A data-quality report generator that finished its API rewrite and has been coasting on small features since.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
textreuse
2.5ANALYTICS
A dormant text-matching package revived, shipped as 1.0.0, and kept current with the tidyverse.
◆ Current state
textreuse detects reused and quoted passages across document collections using minhash and locality-sensitive hashing, with local alignment for inspecting the matches it finds. After years of inactivity, the package reached a 1.0.0 CRAN release in May 2026 that folded accumulated feature work into one version — encoding control on corpus construction, deterministic skipped-document bookkeeping, and an align_local() that returns an empty alignment instead of erroring on non-matching texts. The 1.0.2 release since then is pure compatibility maintenance.
◆ Where it's heading
The arc here is restoration rather than expansion. The work has gone into making the package survivable — silencing deprecated dplyr and tidyr selection and many-to-many join warnings, moving from dead Travis and AppVeyor configs to GitHub Actions, and validating across five R platform and version combinations. Release notes now lead with verification evidence rather than features, which is the signature of a maintainer stabilizing an inherited codebase.
◆ Prediction
Expect continued compatibility releases tracking tidyverse deprecations; nothing in these entries indicates new hashing or alignment capability is planned.
Alternatives to daiquiri and textreuse
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 daiquiri or textreuse.
Tplyr
Tplyr made clinical summary tables explain where every number came from.
rlistings
Clinical listings that keep inheriting their hardest problem — pagination — from the layer below.
hoardr
A cache-directory helper that has shipped nothing but CRAN-triggered patches for seven years.
gigs
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
See all daiquiri alternatives → · See all textreuse alternatives →
Recent activity from daiquiri and textreuse
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 20d agotextreuseCompatibility pass for current dplyr and tidyr
- 3mo agotextreuseCRAN resubmission fixing a moved README URL
- 3mo agotextreuse1.0.0 consolidates years of accumulated feature work
- 1y agodaiquirifield_types_advanced() lets specs name only some columns
- 3y agodaiquirift_strata() splits reports by a column's values
- 3y agodaiquiriColumn-order and integer-column validation fixes
- 3y agodaiquiriReport intermediates write to tempdir(), not the library
- 3y agodaiquiriFirst CRAN release
- 3y agodaiquiriPublic API renamed wholesale for rOpenSci acceptance ⚡
- 10y agotextreuseMinhashes split out from hashes in document objects
Frequently asked questions
What is the difference between daiquiri and textreuse?
Both compete on the same themes — r-package — within Analytics. textreuse is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is daiquiri better than textreuse?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. textreuse is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to daiquiri?
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.
What are the best alternatives to textreuse?
Top textreuse alternatives in Analytics are ranked by recent ship velocity. Browse the "textreuse alternatives" section above for the current picks, or visit /alternatives/textreuse for the full list with editorial commentary on each.