← Back to home
Comparison · Analytics

forcis vs textreuse

A side-by-side editorial comparison of forcis and textreuse — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

forcis vs textreuse: at a glance

Featureforcistextreuse
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesdata-access, r-package, ropensci, oceanographytext-reuse, minhash, lsh, r-package
Last editorial update48m ago3h ago
WebsiteVisit →Visit →

What is forcis?

A foraminifera data-access package whose entire release history is the rOpenSci review process.

forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.

Read the full forcis trajectory →

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.

Read the full textreuse trajectory →

forcis vs textreuse: editorial side-by-side

F
forcis
ANALYTICS
0.0

A foraminifera data-access package whose entire release history is the rOpenSci review process.

◆ Current state

forcis provides R access to the FORCIS database of planktonic foraminifera occurrences. All three releases in the window are review milestones rather than feature work: first stable release, the release answering rOpenSci reviewer comments, and a post-CRAN-review polish. Release notes point at NEWS.md rather than enumerating changes.

◆ Where it's heading

The package is moving from research artifact to reviewed, distributable infrastructure — submitted to rOpenSci at 0.1.0, integrated review feedback at 1.0.0, cleared CRAN at 1.0.1. That arc is complete, so the next phase should be the first release driven by users rather than reviewers.

◆ Prediction

With review and CRAN acceptance both behind it, the next release is most likely to track upstream FORCIS database changes or add query conveniences; the entries themselves say nothing about planned features.

T
textreuse
ANALYTICS
2.5

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 forcis 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 forcis or textreuse.

See all forcis alternatives → · See all textreuse alternatives →

Recent activity from forcis and textreuse

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 20d agotextreuseCompatibility pass for current dplyr and tidyr
  2. 3mo agotextreuseCRAN resubmission fixing a moved README URL
  3. 3mo agotextreuse1.0.0 consolidates years of accumulated feature work
  4. 1y agoforcisPost-CRAN-review example and practice cleanup
  5. 1y agoforcis1.0.0 incorporates rOpenSci review feedback
  6. 1y agoforcisFirst stable release, submitted to rOpenSci
  7. 10y agotextreuseMinhashes split out from hashes in document objects

Frequently asked questions

What is the difference between forcis 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 forcis 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 forcis?

Top forcis alternatives in Analytics are ranked by recent ship velocity. Browse the "forcis alternatives" section above for the current picks, or visit /alternatives/forcis 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.