paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of geos and parallelDist — release velocity, themes, recent moves, and the top alternatives to consider.
The thin GEOS binding for R adds terra interop after three years of compiler triage
geos is a low-overhead R binding to the GEOS geometry engine, exposing predicates, overlays and spatial indexes with minimal copying. Version 0.2.5 accepts terra SpatVector objects directly, alongside fixes for zero-length memcpy and plotting of invalid geometries. The releases between 0.2.0 and 0.2.5 contain almost no feature work — they are responses to compiler warnings, sanitiser findings and CRAN check failures.
parallelDist is in pure preservation mode — one build fix every few years.
parallelDist computes distance matrices across threads in C++ via RcppParallel and Armadillo. The feature set has been settled since 0.2.3 in 2018, which added hamming distance and cosine similarity; everything after that is compatibility work. The most recent release, 0.2.7, exists only to drop a C++11 pin that newer Armadillo versions no longer tolerate.
geos is a low-overhead R binding to the GEOS geometry engine, exposing predicates, overlays and spatial indexes with minimal copying. Version 0.2.5 accepts terra SpatVector objects directly, alongside fixes for zero-length memcpy and plotting of invalid geometries. The releases between 0.2.0 and 0.2.5 contain almost no feature work — they are responses to compiler warnings, sanitiser findings and CRAN check failures.
Feature development stopped after 0.2.0 and the package has since been kept alive against a moving toolchain: strict-prototypes warnings, a clang sanitiser error, format string checks, an M1 test failure. The 0.2.5 terra support breaks that pattern and came from an outside contributor, which suggests the package's direction is now set by what neighbouring spatial packages need from it rather than by GEOS feature coverage.
GEOS has released new capabilities since the 3.11 features wired up in 0.2.0, and none have been exposed since; whether the next release closes that gap or continues as interop-and-maintenance is the open question the history does not yet answer.
parallelDist computes distance matrices across threads in C++ via RcppParallel and Armadillo. The feature set has been settled since 0.2.3 in 2018, which added hamming distance and cosine similarity; everything after that is compatibility work. The most recent release, 0.2.7, exists only to drop a C++11 pin that newer Armadillo versions no longer tolerate.
The package is being kept installable, not developed. The three most recent releases are a toolchain pin removal, a DESCRIPTION field removal, and a coercion change inherited from proxy — none originate from user-facing intent. Gaps of three to four years between releases are the norm now, and each one is triggered by something upstream breaking rather than by a roadmap.
The next release will almost certainly be another compatibility fix timed to whatever Armadillo, Rcpp or CRAN check policy changes next. Nothing in the entries points to new distance measures or API work.
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 geos or parallelDist.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
See all geos alternatives → · See all parallelDist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. geos and parallelDist 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. geos and parallelDist 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 geos alternatives in Analytics are ranked by recent ship velocity. Browse the "geos alternatives" section above for the current picks, or visit /alternatives/geos-r for the full list with editorial commentary on each.
Top parallelDist alternatives in Analytics are ranked by recent ship velocity. Browse the "parallelDist alternatives" section above for the current picks, or visit /alternatives/paralleldist for the full list with editorial commentary on each.