tidytlg
A tables-listings-graphs package that reached CRAN and then went quiet.
Comparison · Analytics
gigs vs textreuse
A side-by-side editorial comparison of gigs and textreuse — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
gigs vs textreuse: at a glance
What is gigs?
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
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.
gigs vs textreuse: editorial side-by-side
gigs
0.0ANALYTICS
gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.
◆ Current state
gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.
◆ Where it's heading
The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.
◆ Prediction
With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.
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 gigs 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 gigs 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.
riem
A weather-data client that keeps rewriting its HTTP layer while slowly tightening its API.
datasetjson
datasetjson rebuilt its object model to track the CDISC Dataset-JSON 1.1 schema.
See all gigs alternatives → · See all textreuse alternatives →
Recent activity from gigs 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 agogigsDocs and Zenodo archiving
- 1y agogigsDocs-only release; nothing changed internally
- 1y agogigsConversion API rewritten around data frames and classify_growth() ⚡
- 2y agogigsDocumentation fixes for autotest compliance
- 2y agogigsINTERGROWTH-21st fetal standards and input validation
- 2y agogigsPatch release with documentation update
- 10y agotextreuseMinhashes split out from hashes in document objects
Frequently asked questions
What is the difference between gigs 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 gigs 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 gigs?
Top gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs 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.