r2rtf
The clinical-report table engine learned Chinese, then learned to leave RTF entirely
Comparison · Analytics
dendroNetwork vs textreuse
A side-by-side editorial comparison of dendroNetwork and textreuse — release velocity, themes, recent moves, and the top alternatives to consider.
dendroNetwork vs textreuse: at a glance
What is dendroNetwork?
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
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.
dendroNetwork vs textreuse: editorial side-by-side
dendroNetwork
0.0ANALYTICS
Six releases, six identical bodies — the feed carries the package abstract instead of release notes
◆ Current state
dendroNetwork builds networks of dendrochronological series from similarity between tree-ring measurements, applies community detection to find matching material, and hands the result to Cytoscape for visualisation. That description is all the feed provides: every one of the six visible releases carries the same package abstract as its body, with no record of what changed in any of them. Version 0.5.5 in July 2025 is the most recent.
◆ Where it's heading
What the timestamps show is more informative than the text. Versions 0.5.0 through 0.5.3 were all published within two minutes of each other on 12 April 2024, and in descending version order, which is the signature of a release history backfilled in one pass rather than four separate releases. Real releases follow at 0.5.4 a fortnight later and 0.5.5 fifteen months after that. Development is slow and, on this evidence, undocumented.
◆ Prediction
No prediction is supportable from these entries — none of them describe a change. Any read on where this package is heading would need the NEWS file or the commit history rather than the feed.
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 dendroNetwork 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 dendroNetwork or textreuse.
DoseFinding
New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing
webmockr
The stubbing library added httr2 support, then spent a year cutting itself free of everything else
crul
crul took mocking back from webmockr and made it a property of the client itself
chattr
chattr deleted every LLM integration it had written and outsourced the lot to ellmer
cloudml
Six years since the last functional change, and Google renamed the service it wraps in the release before that
See all dendroNetwork alternatives → · See all textreuse alternatives →
Recent activity from dendroNetwork 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 agodendroNetworkdendroNetwork 0.5.5
- 2y agodendroNetworkdendroNetwork 0.5.4
- 2y agodendroNetworkdendroNetwork 0.5.0
- 2y agodendroNetworkdendroNetwork 0.5.1
- 2y agodendroNetworkdendroNetwork 0.5.2
- 2y agodendroNetworkdendroNetwork 0.5.3
- 10y agotextreuseMinhashes split out from hashes in document objects
Frequently asked questions
What is the difference between dendroNetwork and textreuse?
They serve adjacent needs but don't currently overlap on shipped themes. 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 dendroNetwork 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 dendroNetwork?
Top dendroNetwork alternatives in Analytics are ranked by recent ship velocity. Browse the "dendroNetwork alternatives" section above for the current picks, or visit /alternatives/dendronetwork 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.